8889841c* 08-22:18:08 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:18:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:18:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:18:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:18: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  * 08-22:18:45 (2925) [INFO] Checking if your system is up to date:  * 08-22:18:45 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:18:45 (3362) [INFO]  * 08-22:18:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:18:46 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:18:46 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:18:46 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:18:46 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:18:46 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:18:46 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:18:46 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:18:46 (3382) [INFO]  * 08-22:18:46 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:18:46 (3362) [INFO]  * 08-22:18:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:18:46 (3372) [INFO] Determining fastest mirrors * 08-22:18:48 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:18:48 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:18:48 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:18:48 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 08-22:19:10 (3372) [INFO]  * 08-22:19:10 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 08-22:19:10 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:19:10 (3382) [INFO]  * 08-22:19:10 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:19:10 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:19:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:19:10 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:19:11 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-08_22:19:11_modified_for_AlmaLinux_8.json * 08-22:19:11 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:19:11 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:14:01 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:14: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  * 09-22:14:37 (2925) [INFO] Checking if your system is up to date:  * 09-22:14:37 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:14:37 (3362) [INFO]  * 09-22:14:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:14:39 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:14:39 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:14:39 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:14:39 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:14:39 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:14:39 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:14:39 (3382) [INFO]  * 09-22:14:39 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:14:39 (3362) [INFO]  * 09-22:14:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:40 (3372) [INFO] Determining fastest mirrors * 09-22:14:41 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 09-22:15:04 (3372) [INFO]  * 09-22:15:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 09-22:15:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:15:05 (3382) [INFO]  * 09-22:15:05 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:15:05 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:15:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:15:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:15:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-09_22:15:06_modified_for_AlmaLinux_8.json * 09-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:15:06 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:15:25 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:15:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:26 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:15: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-22:15:53 (2925) [INFO] Checking if your system is up to date:  * 10-22:15:53 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:15:53 (3362) [INFO]  * 10-22:15:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:15:54 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:15:54 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:15:54 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:15:54 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:15:54 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:15:54 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:15:54 (3382) [INFO]  * 10-22:15:54 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:15:54 (3362) [INFO]  * 10-22:15:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:54 (3372) [INFO] Determining fastest mirrors * 10-22:16:00 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:16:00 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:16:00 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:16:00 (3372) [INFO] * epel: mirrors.coreix.net * 10-22:16:21 (3372) [INFO]  * 10-22:16:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 10-22:16:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:16:21 (3382) [INFO]  * 10-22:16:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:16:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:16:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:16:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:16:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-10_22:16:22_modified_for_AlmaLinux_8.json * 10-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:16:22 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:14:51 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:14:52 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:52 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:52 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:14: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  * 11-22:15:24 (2925) [INFO] Checking if your system is up to date:  * 11-22:15:24 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:15:24 (3362) [INFO]  * 11-22:15:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:15:24 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:15:24 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:15:24 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:15:24 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:15:24 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:15:24 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:15:24 (3382) [INFO]  * 11-22:15:24 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:15:24 (3362) [INFO]  * 11-22:15:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:25 (3372) [INFO] Determining fastest mirrors * 11-22:15:29 (3372) [INFO] * EA4: 185.15.22.168 * 11-22:15:29 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 11-22:15:29 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 11-22:15:29 (3372) [INFO] * epel: mirrors.coreix.net * 11-22:15:49 (3372) [INFO]  * 11-22:15:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 11-22:15:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-22:15:49 (3382) [INFO]  * 11-22:15:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:15:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:15:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:15:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:15:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-11_22:15:50_modified_for_AlmaLinux_8.json * 11-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:15:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:14:17 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:14: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  * 12-22:15:00 (2925) [INFO] Checking if your system is up to date:  * 12-22:15:00 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:15:00 (3362) [INFO]  * 12-22:15:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:01 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:15:01 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:15:01 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:15:01 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:15:01 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:15:01 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:15:02 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:15:02 (3382) [INFO]  * 12-22:15:02 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:15:02 (3362) [INFO]  * 12-22:15:02 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:03 (3372) [INFO] Determining fastest mirrors * 12-22:15:08 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:15:08 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:15:08 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:15:08 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 12-22:15:29 (3372) [INFO]  * 12-22:15:29 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 12-22:15:29 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:15:29 (3382) [INFO]  * 12-22:15:29 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:15:29 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:15:29 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:15:29 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:15:30 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-12_22:15:30_modified_for_AlmaLinux_8.json * 12-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:15:30 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:42 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14:45 (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-22:15:21 (2925) [INFO] Checking if your system is up to date:  * 13-22:15:21 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:15:21 (3362) [INFO]  * 13-22:15:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:15:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:15:22 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:15:22 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:15:22 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:15:22 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:15:22 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:15:22 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:15:22 (3382) [INFO]  * 13-22:15:22 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:15:22 (3362) [INFO]  * 13-22:15:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:15:23 (3372) [INFO] Determining fastest mirrors * 13-22:15:26 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:15:26 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:15:26 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:15:26 (3372) [INFO] * epel: mirrors.coreix.net * 13-22:15:49 (3372) [INFO]  * 13-22:15:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 13-22:15:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:15:49 (3382) [INFO]  * 13-22:15:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:15:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:15:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:15:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:15:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-13_22:15:50_modified_for_AlmaLinux_8.json * 13-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:15:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:14:19 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:14:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:21 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:14: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  * 14-22:15:15 (2925) [INFO] Checking if your system is up to date:  * 14-22:15:15 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:15:15 (3362) [INFO]  * 14-22:15:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:15:15 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:15:15 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:15:15 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:15:15 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:15:15 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:15:16 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:15:16 (3382) [INFO]  * 14-22:15:16 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:15:16 (3362) [INFO]  * 14-22:15:16 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:16 (3372) [INFO] Determining fastest mirrors * 14-22:15:21 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:15:21 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:15:21 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:15:21 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 14-22:15:48 (3372) [INFO]  * 14-22:15:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 14-22:15:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:15:48 (3382) [INFO]  * 14-22:15:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:15:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:15:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:15:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:15:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-14_22:15:49_modified_for_AlmaLinux_8.json * 14-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:15:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:14:28 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:14:30 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:30 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:30 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:14:30 (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-22:15:24 (2925) [INFO] Checking if your system is up to date:  * 15-22:15:24 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:15:24 (3362) [INFO]  * 15-22:15:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:15:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:15:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:15:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:15:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:15:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:15:25 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:15:25 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:15:25 (3382) [INFO]  * 15-22:15:25 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:15:25 (3362) [INFO]  * 15-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:15:25 (3372) [INFO] Determining fastest mirrors * 15-22:15:28 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:15:28 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:15:28 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:15:28 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 15-22:16:09 (3372) [INFO]  * 15-22:16:09 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 15-22:16:09 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:16:09 (3382) [INFO]  * 15-22:16:09 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:16:09 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:16:09 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:16:09 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:16:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-15_22:16:10_modified_for_AlmaLinux_8.json * 15-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:16:10 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:14:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:14: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  * 16-22:14:51 (2925) [INFO] Checking if your system is up to date:  * 16-22:14:51 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:14:51 (3362) [INFO]  * 16-22:14:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:14:51 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:14:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:14:51 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:14:51 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:14:51 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:14:52 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:14:52 (3382) [INFO]  * 16-22:14:52 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:14:52 (3362) [INFO]  * 16-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:52 (3372) [INFO] Determining fastest mirrors * 16-22:14:54 (3372) [INFO] * EA4: 185.15.22.168 * 16-22:14:54 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 16-22:14:54 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 16-22:14:54 (3372) [INFO] * epel: mirrors.coreix.net * 16-22:15:17 (3372) [INFO]  * 16-22:15:17 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 16-22:15:17 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:15:17 (3382) [INFO]  * 16-22:15:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:15:17 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:15:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:15:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:15:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-16_22:15:18_modified_for_AlmaLinux_8.json * 16-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:15:18 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:14:59 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:15:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:02 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:15:02 (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-22:15:35 (2925) [INFO] Checking if your system is up to date:  * 17-22:15:35 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:15:35 (3362) [INFO]  * 17-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:15:36 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:15:36 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:15:36 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:15:36 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:15:36 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:15:36 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:15:36 (3382) [INFO]  * 17-22:15:36 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:15:36 (3362) [INFO]  * 17-22:15:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:36 (3372) [INFO] Determining fastest mirrors * 17-22:15:42 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:15:42 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:15:42 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:15:42 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 17-22:16:02 (3372) [INFO]  * 17-22:16:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 17-22:16:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:16:02 (3382) [INFO]  * 17-22:16:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:16:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:16:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:16:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:16:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-17_22:16:03_modified_for_AlmaLinux_8.json * 17-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:16:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:15:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:15:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:15:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:15:12 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:15:12 (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-22:15:51 (2925) [INFO] Checking if your system is up to date:  * 18-22:15:51 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:15:51 (3362) [INFO]  * 18-22:15:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:15:51 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:15:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:15:51 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:15:51 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:15:51 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:15:52 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:15:52 (3382) [INFO]  * 18-22:15:52 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:15:52 (3362) [INFO]  * 18-22:15:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:53 (3372) [INFO] Determining fastest mirrors * 18-22:15:57 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:15:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:15:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:15:57 (3372) [INFO] * epel: mirrors.coreix.net * 18-22:16:18 (3372) [INFO]  * 18-22:16:18 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 18-22:16:18 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:16:19 (3382) [INFO]  * 18-22:16:19 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:16:19 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:16:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:16:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:16:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-18_22:16:19_modified_for_AlmaLinux_8.json * 18-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:16:20 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:14:13 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:14:15 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:15 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:15 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:14: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  * 19-22:14:47 (2925) [INFO] Checking if your system is up to date:  * 19-22:14:47 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:14:47 (3362) [INFO]  * 19-22:14:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:48 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:14:48 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:14:48 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:14:48 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:14:48 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:14:48 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:14:48 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:14:48 (3382) [INFO]  * 19-22:14:48 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:14:48 (3362) [INFO]  * 19-22:14:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:49 (3372) [INFO] Determining fastest mirrors * 19-22:14:52 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 19-22:15:13 (3372) [INFO]  * 19-22:15:13 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 19-22:15:13 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:15:13 (3382) [INFO]  * 19-22:15:13 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:15:13 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:15:13 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:15:13 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:15:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-19_22:15:14_modified_for_AlmaLinux_8.json * 19-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:15:14 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:14:11 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:13 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:14:13 (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-22:14:52 (2925) [INFO] Checking if your system is up to date:  * 20-22:14:52 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:14:52 (3362) [INFO]  * 20-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:14:52 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:14:52 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:14:52 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:14:52 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:14:52 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:14:53 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:14:53 (3382) [INFO]  * 20-22:14:53 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:14:53 (3362) [INFO]  * 20-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:53 (3372) [INFO] Determining fastest mirrors * 20-22:14:56 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:14:56 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:14:56 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:14:56 (3372) [INFO] * epel: mirrors.coreix.net * 20-22:15:17 (3372) [INFO]  * 20-22:15:17 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 20-22:15:17 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:15:17 (3382) [INFO]  * 20-22:15:17 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:15:17 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:15:17 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:15:17 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:15:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-20_22:15:18_modified_for_AlmaLinux_8.json * 20-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:15:18 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:16:58 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:16:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:16:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:16:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:16: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  * 21-22:17:32 (2925) [INFO] Checking if your system is up to date:  * 21-22:17:32 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:17:32 (3362) [INFO]  * 21-22:17:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:17:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:17:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:17:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:17:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:17:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:17:32 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:17:32 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:17:32 (3382) [INFO]  * 21-22:17:32 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:17:32 (3362) [INFO]  * 21-22:17:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:17:33 (3372) [INFO] Determining fastest mirrors * 21-22:17:38 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:17:38 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:17:38 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:17:38 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 21-22:18:04 (3372) [INFO]  * 21-22:18:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 21-22:18:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:18:04 (3382) [INFO]  * 21-22:18:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:18:04 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:18:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:18:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:18:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-21_22:18:05_modified_for_AlmaLinux_8.json * 21-22:18:05 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:18:05 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:14:09 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:14:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:12 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:14:12 (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-22:14:44 (2925) [INFO] Checking if your system is up to date:  * 22-22:14:44 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:14:44 (3362) [INFO]  * 22-22:14:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:14:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:14:44 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:14:44 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:14:44 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:14:44 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:14:44 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:14:44 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:14:44 (3382) [INFO]  * 22-22:14:44 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:14:44 (3362) [INFO]  * 22-22:14:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:14:45 (3372) [INFO] Determining fastest mirrors * 22-22:14:46 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:14:46 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:14:46 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:14:46 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 22-22:15:07 (3372) [INFO]  * 22-22:15:07 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 22-22:15:07 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:15:07 (3382) [INFO]  * 22-22:15:07 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:15:07 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:15:07 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:15:07 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:15:08 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-22_22:15:08_modified_for_AlmaLinux_8.json * 22-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:15:08 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:14:17 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:14: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  * 23-22:14:54 (2925) [INFO] Checking if your system is up to date:  * 23-22:14:54 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:14:54 (3362) [INFO]  * 23-22:14:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:14:54 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:14:54 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:14:54 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:14:54 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:14:54 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:14:54 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:14:54 (3382) [INFO]  * 23-22:14:54 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:14:54 (3362) [INFO]  * 23-22:14:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:55 (3372) [INFO] Determining fastest mirrors * 23-22:14:59 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:14:59 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:14:59 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:14:59 (3372) [INFO] * epel: mirrors.coreix.net * 23-22:15:21 (3372) [INFO]  * 23-22:15:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 23-22:15:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:15:22 (3382) [INFO]  * 23-22:15:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:15:22 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:15:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:15:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:15:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-23_22:15:23_modified_for_AlmaLinux_8.json * 23-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:15:23 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:16:03 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:16:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:16:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:16:04 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:16: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  * 24-22:16:33 (2925) [INFO] Checking if your system is up to date:  * 24-22:16:33 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:16:33 (3362) [INFO]  * 24-22:16:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:16:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:16:33 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:16:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:16:33 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:16:33 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:16:33 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:16:34 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:16:34 (3382) [INFO]  * 24-22:16:34 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:16:34 (3362) [INFO]  * 24-22:16:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:16:34 (3372) [INFO] Determining fastest mirrors * 24-22:16:38 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:16:38 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:16:38 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:16:38 (3372) [INFO] * epel: mirrors.coreix.net * 24-22:17:03 (3372) [INFO]  * 24-22:17:03 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 24-22:17:03 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:17:04 (3382) [INFO]  * 24-22:17:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:17:04 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:17:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:17:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:17:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-24_22:17:05_modified_for_AlmaLinux_8.json * 24-22:17:05 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:17:05 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:14:55 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:14:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:57 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:14: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  * 25-22:15:28 (2925) [INFO] Checking if your system is up to date:  * 25-22:15:28 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:15:28 (3362) [INFO]  * 25-22:15:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:15:28 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:15:28 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:15:28 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:15:28 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:15:28 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:15:28 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:15:28 (3382) [INFO]  * 25-22:15:28 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:15:28 (3362) [INFO]  * 25-22:15:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:29 (3372) [INFO] Determining fastest mirrors * 25-22:15:33 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:15:33 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:15:33 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:15:33 (3372) [INFO] * epel: mirrors.coreix.net * 25-22:16:02 (3372) [INFO]  * 25-22:16:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 25-22:16:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:16:02 (3382) [INFO]  * 25-22:16:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:16:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:16:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:16:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:16:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-25_22:16:03_modified_for_AlmaLinux_8.json * 25-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:16:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:14:14 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:14:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:16 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:14: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  * 26-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 26-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:14:57 (3362) [INFO]  * 26-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:14:58 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:14:58 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:14:58 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:14:58 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:14:58 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:14:58 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:14:58 (3382) [INFO]  * 26-22:14:58 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:14:58 (3362) [INFO]  * 26-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:58 (3372) [INFO] Determining fastest mirrors * 26-22:15:02 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:15:02 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:15:02 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:15:02 (3372) [INFO] * epel: mirrors.coreix.net * 26-22:15:27 (3372) [INFO]  * 26-22:15:27 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 26-22:15:27 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:15:27 (3382) [INFO]  * 26-22:15:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:15:27 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:15:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:15:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:15:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-26_22:15:28_modified_for_AlmaLinux_8.json * 26-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:15:28 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:08 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14: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  * 27-22:14:45 (2925) [INFO] Checking if your system is up to date:  * 27-22:14:45 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:14:45 (3362) [INFO]  * 27-22:14:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:46 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:14:46 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:14:46 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:14:46 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:14:46 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:14:46 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:14:46 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:14:46 (3382) [INFO]  * 27-22:14:46 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:14:46 (3362) [INFO]  * 27-22:14:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:47 (3372) [INFO] Determining fastest mirrors * 27-22:14:48 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:14:48 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:14:48 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:14:48 (3372) [INFO] * epel: mirrors.coreix.net * 27-22:15:14 (3372) [INFO]  * 27-22:15:14 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 27-22:15:14 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:15:14 (3382) [INFO]  * 27-22:15:14 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:15:14 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:15:14 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:15:14 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:15:15 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-27_22:15:15_modified_for_AlmaLinux_8.json * 27-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:15:15 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:14:12 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:14 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:14: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  * 28-22:14:46 (2925) [INFO] Checking if your system is up to date:  * 28-22:14:46 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:14:46 (3362) [INFO]  * 28-22:14:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:14:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:14:47 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:14:47 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:14:47 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:14:47 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:14:47 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:14:47 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:14:47 (3382) [INFO]  * 28-22:14:47 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:14:47 (3362) [INFO]  * 28-22:14:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:14:47 (3372) [INFO] Determining fastest mirrors * 28-22:14:49 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:14:49 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:14:49 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:14:49 (3372) [INFO] * epel: mir01.syntis.net * 28-22:15:11 (3372) [INFO]  * 28-22:15:11 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 28-22:15:11 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:15:12 (3382) [INFO]  * 28-22:15:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:15:12 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:15:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:15:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:15:12 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-28_22:15:12_modified_for_AlmaLinux_8.json * 28-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:15:13 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-22:14:58 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 29-22:15:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:15:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:15:00 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 29-22:15: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  * 29-22:15:32 (2925) [INFO] Checking if your system is up to date:  * 29-22:15:32 (3361) [INFO] Running: /usr/bin/yum clean all * 29-22:15:32 (3362) [INFO]  * 29-22:15:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 29-22:15:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-22:15:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 29-22:15:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 29-22:15:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 29-22:15:32 (3372) [INFO] : wp-toolkit-thirdparties * 29-22:15:33 (3372) [INFO] Cleaning up list of fastest mirrors * 29-22:15:33 (3382) [INFO]  * 29-22:15:33 (3361) [INFO] Running: /usr/bin/yum check-update * 29-22:15:33 (3362) [INFO]  * 29-22:15:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:33 (3372) [INFO] Determining fastest mirrors * 29-22:15:36 (3372) [INFO] * EA4: 178.18.193.52 * 29-22:15:36 (3372) [INFO] * cpanel-addons-production-feed: 178.18.193.52 * 29-22:15:36 (3372) [INFO] * cpanel-plugins: 178.18.193.52 * 29-22:15:36 (3372) [INFO] * epel: mirrors.coreix.net * 29-22:16:04 (3372) [INFO]  * 29-22:16:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 29-22:16:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-22:16:04 (3382) [INFO]  * 29-22:16:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-22:16:04 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-22:16:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-22:16:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-22:16:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-29_22:16:05_modified_for_AlmaLinux_8.json * 29-22:16:05 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 29-22:16:05 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 30-22:14:54 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:54 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:54 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 30-22:14: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  * 30-22:15:27 (2925) [INFO] Checking if your system is up to date:  * 30-22:15:27 (3361) [INFO] Running: /usr/bin/yum clean all * 30-22:15:27 (3362) [INFO]  * 30-22:15:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:15:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 30-22:15:28 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-22:15:28 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 30-22:15:28 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 30-22:15:28 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 30-22:15:28 (3372) [INFO] : wp-toolkit-thirdparties * 30-22:15:28 (3372) [INFO] Cleaning up list of fastest mirrors * 30-22:15:28 (3382) [INFO]  * 30-22:15:28 (3361) [INFO] Running: /usr/bin/yum check-update * 30-22:15:28 (3362) [INFO]  * 30-22:15:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:15:29 (3372) [INFO] Determining fastest mirrors * 30-22:15:32 (3372) [INFO] * EA4: 185.15.22.168 * 30-22:15:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 30-22:15:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 30-22:15:32 (3372) [INFO] * epel: mirrors.coreix.net * 30-22:15:54 (3372) [INFO]  * 30-22:15:54 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 30-22:15:54 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-22:15:54 (3382) [INFO]  * 30-22:15:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-22:15:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-22:15:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-22:15:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-22:15:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-09-30_22:15:55_modified_for_AlmaLinux_8.json * 30-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 30-22:15:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:15:09 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:15:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:15:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:15:12 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:15:12 (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-22:16:10 (2925) [INFO] Checking if your system is up to date:  * 01-22:16:10 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:16:10 (3362) [INFO]  * 01-22:16:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:16:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:16:11 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:16:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:16:11 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:16:11 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:16:11 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:16:12 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:16:12 (3382) [INFO]  * 01-22:16:12 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:16:12 (3362) [INFO]  * 01-22:16:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:16:13 (3372) [INFO] Determining fastest mirrors * 01-22:16:19 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:16:19 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:16:19 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:16:19 (3372) [INFO] * epel: mirrors.coreix.net * 01-22:16:59 (3372) [INFO]  * 01-22:16:59 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 01-22:16:59 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:16:59 (3382) [INFO]  * 01-22:16:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:16:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:16:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:16:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:17:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-01_22:17:00_modified_for_AlmaLinux_8.json * 01-22:17: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:17:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:15:28 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:15:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:15:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:15:31 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:15: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  * 02-22:16:07 (2925) [INFO] Checking if your system is up to date:  * 02-22:16:07 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:16:07 (3362) [INFO]  * 02-22:16:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:16:08 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:16:08 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:16:08 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:16:08 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:16:08 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:16:08 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:16:09 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:16:09 (3382) [INFO]  * 02-22:16:09 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:16:09 (3362) [INFO]  * 02-22:16:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:16:09 (3372) [INFO] Determining fastest mirrors * 02-22:16:14 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:16:14 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:16:14 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:16:14 (3372) [INFO] * epel: mirrors.coreix.net * 02-22:16:40 (3372) [INFO]  * 02-22:16:40 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 02-22:16:40 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:16:40 (3382) [INFO]  * 02-22:16:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:16:40 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:16:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:16:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:16:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-02_22:16:41_modified_for_AlmaLinux_8.json * 02-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:16:42 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:39 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:43 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:15:20 (2925) [INFO] Checking if your system is up to date:  * 03-22:15:20 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:15:20 (3362) [INFO]  * 03-22:15:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:15:21 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:15:21 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:15:21 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:15:21 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:15:21 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:15:22 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:15:22 (3382) [INFO]  * 03-22:15:22 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:15:22 (3362) [INFO]  * 03-22:15:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:22 (3372) [INFO] Determining fastest mirrors * 03-22:15:27 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:15:27 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:15:27 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:15:27 (3372) [INFO] * epel: mirrors.coreix.net * 03-22:15:48 (3372) [INFO]  * 03-22:15:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 03-22:15:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:15:48 (3382) [INFO]  * 03-22:15:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:15:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:15:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:15:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:15:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-03_22:15:49_modified_for_AlmaLinux_8.json * 03-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:15:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:11 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:14 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14: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  * 04-22:14:52 (2925) [INFO] Checking if your system is up to date:  * 04-22:14:52 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:14:52 (3362) [INFO]  * 04-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:14:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:14:54 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:14:54 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:14:54 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:14:54 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:14:54 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:14:54 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:14:54 (3382) [INFO]  * 04-22:14:54 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:14:54 (3362) [INFO]  * 04-22:14:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:14:54 (3372) [INFO] Determining fastest mirrors * 04-22:14:56 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:14:56 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:14:56 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:14:56 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 04-22:15:19 (3372) [INFO]  * 04-22:15:19 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 04-22:15:19 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:19 (3382) [INFO]  * 04-22:15:19 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:19 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:20 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-04_22:15:20_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:16:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:16:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:16:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:16:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:16: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  * 05-22:16:48 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 05-22:16:48 (3077) [ERROR] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/ed7c864d5a6077ad25456059cc1cce9455092bc004a4ffe690f2873c7c239229-prestodelta.xml.gz: [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/.  * 05-22:16:48 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 05-22:16:48 (2925) [INFO] Checking if your system is up to date:  * 05-22:16:48 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:16:48 (3362) [INFO]  * 05-22:16:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:16:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:16:49 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:16:49 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:16:49 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:16:49 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:16:49 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:16:49 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:16:49 (3382) [INFO]  * 05-22:16:49 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:16:49 (3362) [INFO]  * 05-22:16:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:16:49 (3372) [INFO] Determining fastest mirrors * 05-22:16:54 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:16:54 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:16:54 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:16:54 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 05-22:16:57 (3372) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/68ac849eb8cd7684fe8a82f2689db3c82b27a5230cf5b2b8ae673198c5f239d5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 05-22:16:57 (3372) [INFO] Trying other mirror. * 05-22:16:57 (3372) [INFO] To address this issue please refer to the below wiki article  * 05-22:16:57 (3372) [INFO]  * 05-22:16:57 (3372) [INFO] https://wiki.centos.org/yum-errors * 05-22:16:57 (3372) [INFO]  * 05-22:16:57 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 05-22:16:57 (3372) [INFO]  * 05-22:17:15 (3372) [INFO]  * 05-22:17:15 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 05-22:17:15 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:17:16 (3382) [INFO]  * 05-22:17:16 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:17:16 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:17:16 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:17:16 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:17:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-05_22:17:16_modified_for_AlmaLinux_8.json * 05-22:17: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:17:17 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:14:30 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:31 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:14: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  * 06-22:15:14 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 06-22:15:14 (3077) [ERROR] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/ed7c864d5a6077ad25456059cc1cce9455092bc004a4ffe690f2873c7c239229-prestodelta.xml.gz: [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://mir01.syntis.net/epel/7/x86_64/repodata/8ee167a3ed1e5c9b035eda2f19b242f2d763ece9aa52606c3209f731c3af829d-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror.  * 06-22:15:14 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 06-22:15:14 (2925) [INFO] Checking if your system is up to date:  * 06-22:15:14 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:15:14 (3362) [INFO]  * 06-22:15:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:15:15 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:15:15 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:15:15 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:15:15 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:15:15 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:15:15 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:15:15 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:15:15 (3382) [INFO]  * 06-22:15:15 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:15:15 (3362) [INFO]  * 06-22:15:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:15:15 (3372) [INFO] Determining fastest mirrors * 06-22:15:21 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:15:21 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:15:21 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:15:21 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 06-22:15:23 (3372) [INFO] https://mir01.syntis.net/epel/7/x86_64/repodata/765fa10a99e4650599932a2db64842caf0e770f3ce0b67495927eefec6d7d7fb-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 06-22:15:23 (3372) [INFO] Trying other mirror. * 06-22:15:23 (3372) [INFO] To address this issue please refer to the below wiki article  * 06-22:15:23 (3372) [INFO]  * 06-22:15:23 (3372) [INFO] https://wiki.centos.org/yum-errors * 06-22:15:23 (3372) [INFO]  * 06-22:15:23 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 06-22:15:23 (3372) [INFO]  * 06-22:15:23 (3372) [INFO] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/68ac849eb8cd7684fe8a82f2689db3c82b27a5230cf5b2b8ae673198c5f239d5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 06-22:15:23 (3372) [INFO] Trying other mirror. * 06-22:15:25 (3372) [INFO] https://mir01.syntis.net/epel/7/x86_64/repodata/68ac849eb8cd7684fe8a82f2689db3c82b27a5230cf5b2b8ae673198c5f239d5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 06-22:15:25 (3372) [INFO] Trying other mirror. * 06-22:15:26 (3372) [INFO] http://mirrors.coreix.net/fedora-epel/7/x86_64/repodata/68ac849eb8cd7684fe8a82f2689db3c82b27a5230cf5b2b8ae673198c5f239d5-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 06-22:15:26 (3372) [INFO] Trying other mirror. * 06-22:15:26 (3372) [INFO] https://mirrors.ukfast.co.uk/sites/dl.fedoraproject.org/pub/epel/7/x86_64/repodata/68ac849eb8cd7684fe8a82f2689db3c82b27a5230cf5b2b8ae673198c5f239d5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 06-22:15:26 (3372) [INFO] Trying other mirror. * 06-22:15:43 (3372) [INFO]  * 06-22:15:43 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 06-22:15:43 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:15:43 (3382) [INFO]  * 06-22:15:43 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:15:43 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:15:43 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:15:43 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:15:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-06_22:15:44_modified_for_AlmaLinux_8.json * 06-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:15:45 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:14:27 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:28 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:28 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:28 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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  * 07-22:15:03 (2925) [INFO] Checking if your system is up to date:  * 07-22:15:03 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:15:03 (3362) [INFO]  * 07-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:03 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:15:03 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:15:03 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:15:03 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:15:03 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:15:03 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:15:04 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:15:04 (3382) [INFO]  * 07-22:15:04 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:15:04 (3362) [INFO]  * 07-22:15:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:05 (3372) [INFO] Determining fastest mirrors * 07-22:15:09 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:15:09 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:15:09 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:15:09 (3372) [INFO] * epel: mirrors.coreix.net * 07-22:15:30 (3372) [INFO]  * 07-22:15:30 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 07-22:15:30 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:15:31 (3382) [INFO]  * 07-22:15:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:15:31 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:15:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:15:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:15:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-07_22:15:32_modified_for_AlmaLinux_8.json * 07-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:15:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:15:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:15:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:15:23 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:15: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  * 08-22:15:59 (2925) [INFO] Checking if your system is up to date:  * 08-22:15:59 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:15:59 (3362) [INFO]  * 08-22:16:00 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:16:00 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:16:00 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:16:00 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:16:00 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:16:00 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:16:00 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:16:01 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:16:01 (3382) [INFO]  * 08-22:16:01 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:16:01 (3362) [INFO]  * 08-22:16:01 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:16:02 (3372) [INFO] Determining fastest mirrors * 08-22:16:09 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:16:09 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:16:09 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:16:09 (3372) [INFO] * epel: mirrors.coreix.net * 08-22:16:32 (3372) [INFO]  * 08-22:16:32 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 08-22:16:32 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:16:32 (3382) [INFO]  * 08-22:16:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:16:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:16:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:16:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:16:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-08_22:16:33_modified_for_AlmaLinux_8.json * 08-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:16:33 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:15:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:15:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:15:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:15:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:15: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  * 09-22:15:49 (2925) [INFO] Checking if your system is up to date:  * 09-22:15:49 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:15:49 (3362) [INFO]  * 09-22:15:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:15:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:15:49 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:15:49 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:15:49 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:15:49 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:15:49 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:15:49 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:15:49 (3382) [INFO]  * 09-22:15:49 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:15:49 (3362) [INFO]  * 09-22:15:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:15:50 (3372) [INFO] Determining fastest mirrors * 09-22:15:54 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:15:54 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:15:54 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:15:54 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 09-22:15:57 (3372) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/44adffa91151710960f5dc913d9adc96f7acaac9f3d0011ea81a6923255eecc0-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 09-22:15:57 (3372) [INFO] Trying other mirror. * 09-22:15:57 (3372) [INFO] To address this issue please refer to the below wiki article  * 09-22:15:57 (3372) [INFO]  * 09-22:15:57 (3372) [INFO] https://wiki.centos.org/yum-errors * 09-22:15:57 (3372) [INFO]  * 09-22:15:57 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 09-22:15:57 (3372) [INFO]  * 09-22:16:15 (3372) [INFO]  * 09-22:16:15 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 09-22:16:15 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:16:15 (3382) [INFO]  * 09-22:16:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:16:15 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:16:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:16:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:16:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-09_22:16:16_modified_for_AlmaLinux_8.json * 09-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:16:16 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:14:23 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:25 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:14: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  * 10-22:14:59 (2925) [INFO] Checking if your system is up to date:  * 10-22:14:59 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:14:59 (3362) [INFO]  * 10-22:14:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:14:59 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:14:59 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:14:59 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:14:59 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:14:59 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:14:59 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:14:59 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:14:59 (3382) [INFO]  * 10-22:14:59 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:14:59 (3362) [INFO]  * 10-22:14:59 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:00 (3372) [INFO] Determining fastest mirrors * 10-22:15:11 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:15:11 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:15:11 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:15:11 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 10-22:15:34 (3372) [INFO]  * 10-22:15:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 10-22:15:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:15:34 (3382) [INFO]  * 10-22:15:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:15:34 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:15:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:15:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:15:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-10_22:15:35_modified_for_AlmaLinux_8.json * 10-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:15:36 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:17:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:17:17 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:17:17 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:17:17 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:17: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  * 11-22:17:45 (2925) [INFO] Checking if your system is up to date:  * 11-22:17:45 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:17:45 (3362) [INFO]  * 11-22:17:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:17:46 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:17:46 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:17:46 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:17:46 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:17:46 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:17:46 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:17:46 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:17:46 (3382) [INFO]  * 11-22:17:46 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:17:46 (3362) [INFO]  * 11-22:17:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:17:47 (3372) [INFO] Determining fastest mirrors * 11-22:17:50 (3372) [INFO] * EA4: 185.15.22.168 * 11-22:17:50 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 11-22:17:50 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 11-22:17:50 (3372) [INFO] * epel: mirrors.coreix.net * 11-22:18:12 (3372) [INFO]  * 11-22:18:12 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 11-22:18:12 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-22:18:12 (3382) [INFO]  * 11-22:18:12 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:18:12 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:18:12 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:18:12 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:18:13 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-11_22:18:13_modified_for_AlmaLinux_8.json * 11-22:18: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:18:13 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:14:17 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:14: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  * 12-22:14:54 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 12-22:14:54 (3077) [ERROR] http://mirrors.coreix.net/fedora-epel/7/x86_64/repodata/6626423c0ee0560a872a3ff029a1b49e91cb0956d6921975a007ef965653039c-prestodelta.xml.gz: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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://lon.mirror.rackspace.com/epel/7/x86_64/repodata/c02b93c22a24a03d1ab945bed2220201b5ea4c80381a825b5b4438022b5ce61b-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. http://mirrors.coreix.net/fedora-epel/7/x86_64/repodata/c02b93c22a24a03d1ab945bed2220201b5ea4c80381a825b5b4438022b5ce61b-other.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. https://mir01.syntis.net/epel/7/x86_64/repodata/c02b93c22a24a03d1ab945bed2220201b5ea4c80381a825b5b4438022b5ce61b-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror.  * 12-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 12-22:14:54 (2925) [INFO] Checking if your system is up to date:  * 12-22:14:54 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:14:54 (3362) [INFO]  * 12-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:14:55 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:14:55 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:14:55 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:14:55 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:14:55 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:14:55 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:14:55 (3382) [INFO]  * 12-22:14:55 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:14:55 (3362) [INFO]  * 12-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:56 (3372) [INFO] Determining fastest mirrors * 12-22:14:57 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:14:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:14:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:14:57 (3372) [INFO] * epel: mirrors.coreix.net * 12-22:15:02 (3372) [INFO] http://mirrors.coreix.net/fedora-epel/7/x86_64/repodata/691cb47bd594e2b8d64b316255d60dc0cf130d5cea1e9a49b8a95aa1a0464389-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found * 12-22:15:02 (3372) [INFO] Trying other mirror. * 12-22:15:02 (3372) [INFO] To address this issue please refer to the below wiki article  * 12-22:15:02 (3372) [INFO]  * 12-22:15:02 (3372) [INFO] https://wiki.centos.org/yum-errors * 12-22:15:02 (3372) [INFO]  * 12-22:15:02 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 12-22:15:02 (3372) [INFO]  * 12-22:15:03 (3372) [INFO] http://mirrors.coreix.net/fedora-epel/7/x86_64/repodata/abf4e872f1305665ad77291b64d1157916361583c6914b184b5d6cb3a8a09953-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found * 12-22:15:03 (3372) [INFO] Trying other mirror. * 12-22:15:05 (3372) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/abf4e872f1305665ad77291b64d1157916361583c6914b184b5d6cb3a8a09953-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 12-22:15:05 (3372) [INFO] Trying other mirror. * 12-22:15:25 (3372) [INFO]  * 12-22:15:25 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 12-22:15:25 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:15:25 (3382) [INFO]  * 12-22:15:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:15:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:15:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:15:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:15:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-12_22:15:26_modified_for_AlmaLinux_8.json * 12-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:15:26 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14: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  * 13-22:14:54 (2925) [INFO] Checking if your system is up to date:  * 13-22:14:54 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:14:54 (3362) [INFO]  * 13-22:14:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:54 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:14:54 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:14:54 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:14:54 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:14:54 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:14:54 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:14:54 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:14:54 (3382) [INFO]  * 13-22:14:54 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:14:54 (3362) [INFO]  * 13-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:55 (3372) [INFO] Determining fastest mirrors * 13-22:14:57 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:14:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:14:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:14:57 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 13-22:15:21 (3372) [INFO]  * 13-22:15:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 13-22:15:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:15:21 (3382) [INFO]  * 13-22:15:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:15:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:15:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:15:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-13_22:15:22_modified_for_AlmaLinux_8.json * 13-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:15:23 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:14:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:14: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  * 14-22:14:56 (2925) [INFO] Checking if your system is up to date:  * 14-22:14:56 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:14:56 (3362) [INFO]  * 14-22:14:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:14:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:14:56 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:14:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:14:56 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:14:56 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:14:56 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:14:57 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:14:57 (3382) [INFO]  * 14-22:14:57 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:14:57 (3362) [INFO]  * 14-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:14:57 (3372) [INFO] Determining fastest mirrors * 14-22:15:00 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 14-22:15:25 (3372) [INFO]  * 14-22:15:25 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 14-22:15:25 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:15:25 (3382) [INFO]  * 14-22:15:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:15:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:15:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:15:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:15:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-14_22:15:26_modified_for_AlmaLinux_8.json * 14-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:15:26 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:15:32 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:15:35 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:15:35 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:15:35 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:15: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  * 15-22:16:08 (2925) [INFO] Checking if your system is up to date:  * 15-22:16:08 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:16:08 (3362) [INFO]  * 15-22:16:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:16:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:16:09 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:16:09 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:16:09 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:16:09 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:16:09 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:16:09 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:16:09 (3382) [INFO]  * 15-22:16:09 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:16:09 (3362) [INFO]  * 15-22:16:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:16:10 (3372) [INFO] Determining fastest mirrors * 15-22:16:16 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:16:16 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:16:16 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:16:16 (3372) [INFO] * epel: mirrors.coreix.net * 15-22:16:39 (3372) [INFO]  * 15-22:16:39 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 15-22:16:39 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:16:39 (3382) [INFO]  * 15-22:16:39 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:16:39 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:16:39 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:16:39 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:16:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-15_22:16:40_modified_for_AlmaLinux_8.json * 15-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:16:40 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:15:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:15:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:15:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:15:08 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:15:08 (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-22:15:46 (2925) [INFO] Checking if your system is up to date:  * 16-22:15:46 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:15:46 (3362) [INFO]  * 16-22:15:46 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:15:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:15:47 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:15:47 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:15:47 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:15:47 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:15:47 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:15:47 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:15:47 (3382) [INFO]  * 16-22:15:47 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:15:47 (3362) [INFO]  * 16-22:15:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:15:47 (3372) [INFO] Determining fastest mirrors * 16-22:15:52 (3372) [INFO] * EA4: 185.15.22.168 * 16-22:15:52 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 16-22:15:52 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 16-22:15:52 (3372) [INFO] * epel: mirrors.coreix.net * 16-22:16:15 (3372) [INFO]  * 16-22:16:15 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 16-22:16:15 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:16:15 (3382) [INFO]  * 16-22:16:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:16:15 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:16:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:16:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:16:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-16_22:16:16_modified_for_AlmaLinux_8.json * 16-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:16:16 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:14:19 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:25 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:14: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  * 17-22:15:06 (2925) [INFO] Checking if your system is up to date:  * 17-22:15:06 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:15:06 (3362) [INFO]  * 17-22:15:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:15:06 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:15:06 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:15:06 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:15:06 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:15:06 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:15:07 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:15:07 (3382) [INFO]  * 17-22:15:07 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:15:07 (3362) [INFO]  * 17-22:15:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:07 (3372) [INFO] Determining fastest mirrors * 17-22:15:21 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:15:21 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:15:21 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:15:21 (3372) [INFO] * epel: mirrors.coreix.net * 17-22:15:42 (3372) [INFO]  * 17-22:15:42 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 17-22:15:42 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:15:43 (3382) [INFO]  * 17-22:15:43 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:15:43 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:15:43 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:15:43 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:15:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-17_22:15:43_modified_for_AlmaLinux_8.json * 17-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:15: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.  * 17-22:15:44 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:14:23 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:25 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:25 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:14: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  * 18-22:15:11 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 18-22:15:11 (3077) [ERROR] Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 14: HTTPS Error 503 - Service Unavailable  * 18-22:15:11 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 18-22:15:11 (2925) [INFO] Checking if your system is up to date:  * 18-22:15:11 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:15:11 (3362) [INFO]  * 18-22:15:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:15:11 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:15:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:15:11 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:15:11 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:15:11 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:15:12 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:15:12 (3382) [INFO]  * 18-22:15:12 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:15:12 (3362) [INFO]  * 18-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:13 (3372) [INFO] Determining fastest mirrors * 18-22:15:17 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 18-22:15:20 (3372) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/7fdac9f08385054289ff75f6f777678e26f1b76a64d8e58e7a6a43e80e805161-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 18-22:15:20 (3372) [INFO] Trying other mirror. * 18-22:15:20 (3372) [INFO] To address this issue please refer to the below wiki article  * 18-22:15:20 (3372) [INFO]  * 18-22:15:20 (3372) [INFO] https://wiki.centos.org/yum-errors * 18-22:15:20 (3372) [INFO]  * 18-22:15:20 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 18-22:15:20 (3372) [INFO]  * 18-22:15:39 (3372) [INFO]  * 18-22:15:39 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 18-22:15:39 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:15:39 (3382) [INFO]  * 18-22:15:39 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:15:39 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:15:39 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:15:39 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:15:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-18_22:15:40_modified_for_AlmaLinux_8.json * 18-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:15: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.  * 18-22:15:40 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:14:06 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:14:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:08 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:14:08 (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-22:14:47 (2925) [INFO] Checking if your system is up to date:  * 19-22:14:47 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:14:47 (3362) [INFO]  * 19-22:14:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:48 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:14:48 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:14:48 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:14:48 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:14:48 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:14:48 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:14:48 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:14:48 (3382) [INFO]  * 19-22:14:48 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:14:48 (3362) [INFO]  * 19-22:14:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:48 (3372) [INFO] Determining fastest mirrors * 19-22:14:52 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:14:52 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 19-22:15:13 (3372) [INFO]  * 19-22:15:13 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 19-22:15:13 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:15:13 (3382) [INFO]  * 19-22:15:13 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:15:13 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:15:13 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:15:13 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:15:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-19_22:15:14_modified_for_AlmaLinux_8.json * 19-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:15: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.  * 19-22:15:14 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:14:23 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:26 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:14: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-22:14:57 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 20-22:14:57 (3077) [ERROR] https://mir01.syntis.net/epel/7/x86_64/repodata/1c241dffd9684c1f6349a3c7a81688cd407ddf0970dec630905a1850e401236b-prestodelta.xml.gz: [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://lon.mirror.rackspace.com/epel/7/x86_64/repodata/f00d4e6fec1ddabc2b481582367e4d27dac19e19aaa52eb0e5959a136d61f6a9-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror.  * 20-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 20-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 20-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:14:57 (3362) [INFO]  * 20-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:14:57 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:14:57 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:14:57 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:14:57 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:14:57 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:14:58 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:14:58 (3382) [INFO]  * 20-22:14:58 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:14:58 (3362) [INFO]  * 20-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:58 (3372) [INFO] Determining fastest mirrors * 20-22:15:02 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:15:02 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:15:02 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:15:02 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 20-22:15:05 (3372) [INFO] https://mir01.syntis.net/epel/7/x86_64/repodata/c56f538d6c401067baef087a4e60271ad4aafbf2b5db16e6b9e3087d04b075c1-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 20-22:15:05 (3372) [INFO] Trying other mirror. * 20-22:15:05 (3372) [INFO] To address this issue please refer to the below wiki article  * 20-22:15:05 (3372) [INFO]  * 20-22:15:05 (3372) [INFO] https://wiki.centos.org/yum-errors * 20-22:15:05 (3372) [INFO]  * 20-22:15:05 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 20-22:15:05 (3372) [INFO]  * 20-22:15:05 (3372) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/0304745656d9b774b52f8636de4ade5d1221c20aa62f4e1ac690250fcf5e6148-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 20-22:15:05 (3372) [INFO] Trying other mirror. * 20-22:15:07 (3372) [INFO] https://mir01.syntis.net/epel/7/x86_64/repodata/0304745656d9b774b52f8636de4ade5d1221c20aa62f4e1ac690250fcf5e6148-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 20-22:15:07 (3372) [INFO] Trying other mirror. * 20-22:15:27 (3372) [INFO]  * 20-22:15:27 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 20-22:15:27 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:15:28 (3382) [INFO]  * 20-22:15:28 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:15:28 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:15:28 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:15:28 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:15:29 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-20_22:15:29_modified_for_AlmaLinux_8.json * 20-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:15: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.  * 20-22:15:29 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:14:06 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:14: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  * 21-22:14:48 (2925) [INFO] Checking if your system is up to date:  * 21-22:14:48 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:14:48 (3362) [INFO]  * 21-22:14:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:48 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:14:48 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:14:48 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:14:48 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:14:48 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:14:48 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:14:48 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:14:48 (3382) [INFO]  * 21-22:14:48 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:14:48 (3362) [INFO]  * 21-22:14:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:49 (3372) [INFO] Determining fastest mirrors * 21-22:14:54 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:14:54 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:14:54 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:14:54 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 21-22:15:20 (3372) [INFO]  * 21-22:15:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 21-22:15:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:15:21 (3382) [INFO]  * 21-22:15:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:15:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:15:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:15:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-21_22:15:22_modified_for_AlmaLinux_8.json * 21-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:15: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-22:15:22 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:15:05 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:15:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:08 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:08 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:15:08 (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-22:15:44 (2925) [INFO] Checking if your system is up to date:  * 22-22:15:44 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:15:44 (3362) [INFO]  * 22-22:15:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:15:44 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:15:44 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:15:44 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:15:44 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:15:44 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:15:44 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:15:44 (3382) [INFO]  * 22-22:15:44 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:15:44 (3362) [INFO]  * 22-22:15:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:45 (3372) [INFO] Determining fastest mirrors * 22-22:15:50 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 22-22:16:10 (3372) [INFO]  * 22-22:16:10 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 22-22:16:10 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:16:10 (3382) [INFO]  * 22-22:16:10 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:16:10 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:16:10 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:16:10 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:16:11 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-22_22:16:11_modified_for_AlmaLinux_8.json * 22-22:16:11 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:16: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.  * 22-22:16:11 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:15:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:15:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:15:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:15:05 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:15:05 (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-22:15:36 (2925) [INFO] Checking if your system is up to date:  * 23-22:15:36 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:15:36 (3362) [INFO]  * 23-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:15:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:15:37 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:15:37 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:15:37 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:15:37 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:15:37 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:15:37 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:15:37 (3382) [INFO]  * 23-22:15:37 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:15:37 (3362) [INFO]  * 23-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:15:37 (3372) [INFO] Determining fastest mirrors * 23-22:15:41 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:15:41 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:15:41 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:15:41 (3372) [INFO] * epel: fedora.mirrorservice.org * 23-22:16:02 (3372) [INFO]  * 23-22:16:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 23-22:16:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:16:02 (3382) [INFO]  * 23-22:16:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:16:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:16:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:16:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:16:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-23_22:16:03_modified_for_AlmaLinux_8.json * 23-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:16: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.  * 23-22:16:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:14:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:14: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  * 24-22:14:52 (2925) [INFO] Checking if your system is up to date:  * 24-22:14:52 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:14:52 (3362) [INFO]  * 24-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:14:52 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:14:52 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:14:52 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:14:52 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:14:52 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:14:52 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:14:52 (3382) [INFO]  * 24-22:14:52 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:14:52 (3362) [INFO]  * 24-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:53 (3372) [INFO] Determining fastest mirrors * 24-22:14:55 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:14:55 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:14:55 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:14:55 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 24-22:15:27 (3372) [INFO]  * 24-22:15:27 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 24-22:15:27 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:15:27 (3382) [INFO]  * 24-22:15:27 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:15:27 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:15:27 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:15:27 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:15:28 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-24_22:15:28_modified_for_AlmaLinux_8.json * 24-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:15: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.  * 24-22:15:29 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:14:24 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:26 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:14: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  * 25-22:15:03 (2925) [INFO] Checking if your system is up to date:  * 25-22:15:03 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:15:03 (3362) [INFO]  * 25-22:15:04 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:04 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:15:04 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:15:04 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:15:04 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:15:04 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:15:04 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:15:05 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:15:05 (3382) [INFO]  * 25-22:15:05 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:15:05 (3362) [INFO]  * 25-22:15:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:06 (3372) [INFO] Determining fastest mirrors * 25-22:15:11 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:15:11 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:15:11 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:15:11 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 25-22:15:35 (3372) [INFO]  * 25-22:15:35 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 25-22:15:35 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:15:35 (3382) [INFO]  * 25-22:15:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:15:35 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:15:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:15:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:15:36 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-25_22:15:36_modified_for_AlmaLinux_8.json * 25-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:15: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.  * 25-22:15:36 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:14: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  * 26-22:15:38 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 26-22:15:38 (3077) [ERROR] https://mir01.syntis.net/epel/7/x86_64/repodata/2a347cd13737bf1e02be044ef0a2c72948a91b857b05574922fe78748357c813-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/.  * 26-22:15:38 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 26-22:15:39 (2925) [INFO] Checking if your system is up to date:  * 26-22:15:39 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:15:39 (3362) [INFO]  * 26-22:15:40 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:40 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:15:40 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:15:40 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:15:40 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:15:40 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:15:40 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:15:41 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:15:41 (3382) [INFO]  * 26-22:15:41 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:15:41 (3362) [INFO]  * 26-22:15:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:42 (3372) [INFO] Determining fastest mirrors * 26-22:15:46 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:15:46 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:15:46 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:15:46 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 26-22:16:14 (3372) [INFO]  * 26-22:16:14 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 26-22:16:14 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:16:15 (3382) [INFO]  * 26-22:16:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:16:15 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:16:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:16:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:16:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-26_22:16:16_modified_for_AlmaLinux_8.json * 26-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:16: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.  * 26-22:16:16 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:14 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14: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  * 27-22:14:50 (2925) [INFO] Checking if your system is up to date:  * 27-22:14:50 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:14:50 (3362) [INFO]  * 27-22:14:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:14:51 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:14:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:14:51 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:14:51 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:14:51 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:14:51 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:14:51 (3382) [INFO]  * 27-22:14:51 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:14:51 (3362) [INFO]  * 27-22:14:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:51 (3372) [INFO] Determining fastest mirrors * 27-22:14:53 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:14:53 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:14:53 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:14:53 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 27-22:15:18 (3372) [INFO]  * 27-22:15:18 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 27-22:15:18 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:15:18 (3382) [INFO]  * 27-22:15:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:15:18 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:15:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:15:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:15:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-27_22:15:19_modified_for_AlmaLinux_8.json * 27-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:15: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.  * 27-22:15:19 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:14:28 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:31 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:14: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-22:15:25 (2925) [INFO] Checking if your system is up to date:  * 28-22:15:25 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:15:25 (3362) [INFO]  * 28-22:15:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:26 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:15:26 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:15:26 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:15:26 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:15:26 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:15:26 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:15:26 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:15:26 (3382) [INFO]  * 28-22:15:26 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:15:26 (3362) [INFO]  * 28-22:15:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:27 (3372) [INFO] Determining fastest mirrors * 28-22:15:30 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:15:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:15:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:15:30 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 28-22:15:53 (3372) [INFO]  * 28-22:15:53 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 28-22:15:53 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:15:54 (3382) [INFO]  * 28-22:15:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:15:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:15:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:15:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:15:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-28_22:15:54_modified_for_AlmaLinux_8.json * 28-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:15: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.  * 28-22:15:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-22:15:03 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 29-22:15:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:15:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:15:06 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 29-22:15: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  * 29-22:15:37 (2925) [INFO] Checking if your system is up to date:  * 29-22:15:37 (3361) [INFO] Running: /usr/bin/yum clean all * 29-22:15:37 (3362) [INFO]  * 29-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 29-22:15:37 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-22:15:37 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 29-22:15:37 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 29-22:15:37 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 29-22:15:37 (3372) [INFO] : wp-toolkit-thirdparties * 29-22:15:37 (3372) [INFO] Cleaning up list of fastest mirrors * 29-22:15:37 (3382) [INFO]  * 29-22:15:37 (3361) [INFO] Running: /usr/bin/yum check-update * 29-22:15:37 (3362) [INFO]  * 29-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:38 (3372) [INFO] Determining fastest mirrors * 29-22:15:43 (3372) [INFO] * EA4: 185.15.22.168 * 29-22:15:43 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 29-22:15:43 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 29-22:15:43 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 29-22:16:02 (3372) [INFO]  * 29-22:16:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 29-22:16:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-22:16:02 (3382) [INFO]  * 29-22:16:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-22:16:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-22:16:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-22:16:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-22:16:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-29_22:16:03_modified_for_AlmaLinux_8.json * 29-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 29-22:16: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.  * 29-22:16:04 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-22:15:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 30-22:15:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:15:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:15:20 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 30-22:15: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  * 30-22:15:56 (2925) [INFO] Checking if your system is up to date:  * 30-22:15:56 (3361) [INFO] Running: /usr/bin/yum clean all * 30-22:15:56 (3362) [INFO]  * 30-22:15:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:15:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 30-22:15:56 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-22:15:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 30-22:15:56 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 30-22:15:56 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 30-22:15:56 (3372) [INFO] : wp-toolkit-thirdparties * 30-22:15:57 (3372) [INFO] Cleaning up list of fastest mirrors * 30-22:15:57 (3382) [INFO]  * 30-22:15:57 (3361) [INFO] Running: /usr/bin/yum check-update * 30-22:15:57 (3362) [INFO]  * 30-22:15:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:15:57 (3372) [INFO] Determining fastest mirrors * 30-22:16:03 (3372) [INFO] * EA4: 185.15.22.168 * 30-22:16:03 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 30-22:16:03 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 30-22:16:03 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 30-22:16:29 (3372) [INFO]  * 30-22:16:29 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 30-22:16:29 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-22:16:29 (3382) [INFO]  * 30-22:16:29 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-22:16:29 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-22:16:30 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-22:16:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-22:16:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-30_22:16:32_modified_for_AlmaLinux_8.json * 30-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 30-22:16: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.  * 30-22:16:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 31-22:15:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 31-22:15:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:15:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:15:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 31-22:15: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  * 31-22:15:44 (2925) [INFO] Checking if your system is up to date:  * 31-22:15:44 (3361) [INFO] Running: /usr/bin/yum clean all * 31-22:15:44 (3362) [INFO]  * 31-22:15:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:15:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 31-22:15:44 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-22:15:44 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 31-22:15:44 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 31-22:15:44 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 31-22:15:44 (3372) [INFO] : wp-toolkit-thirdparties * 31-22:15:44 (3372) [INFO] Cleaning up list of fastest mirrors * 31-22:15:44 (3382) [INFO]  * 31-22:15:44 (3361) [INFO] Running: /usr/bin/yum check-update * 31-22:15:44 (3362) [INFO]  * 31-22:15:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:15:45 (3372) [INFO] Determining fastest mirrors * 31-22:15:48 (3372) [INFO] * EA4: 185.15.22.168 * 31-22:15:48 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 31-22:15:48 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 31-22:15:48 (3372) [INFO] * epel: mirrors.20i.com * 31-22:16:18 (3372) [INFO] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 31-22:16:18 (3372) [INFO] Trying other mirror. * 31-22:16:39 (3372) [INFO]  * 31-22:16:39 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 31-22:16:39 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-22:16:39 (3382) [INFO]  * 31-22:16:39 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-22:16:39 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-22:16:39 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 31-22:16:39 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 31-22:16:40 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-10-31_22:16:40_modified_for_AlmaLinux_8.json * 31-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 31-22:16: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.  * 31-22:16:40 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:14:10 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:13 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:14:13 (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-22:14:46 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 01-22:14:46 (3077) [ERROR] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/24046e001e45ac2cacef15d67f9d97e50ae90716041d1a7c6e650688930e8f81-prestodelta.xml.gz: [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://mir01.syntis.net/epel/7/x86_64/repodata/31d94802a7feb3d4b9b50834853a761b91355276d0e4a41fc35e4780cd5d1303-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror.  * 01-22:14:46 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 01-22:14:47 (2925) [INFO] Checking if your system is up to date:  * 01-22:14:47 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:14:47 (3362) [INFO]  * 01-22:14:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:47 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:14:47 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:14:47 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:14:47 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:14:47 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:14:47 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:14:47 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:14:47 (3382) [INFO]  * 01-22:14:47 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:14:47 (3362) [INFO]  * 01-22:14:47 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:48 (3372) [INFO] Determining fastest mirrors * 01-22:14:51 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:14:51 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:14:51 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:14:51 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 01-22:14:55 (3372) [INFO] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/e515cd75b2b8548e7aec0cb2ea02b138a0d2ff7098324b0be8cc08e6ac290901-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 01-22:14:55 (3372) [INFO] Trying other mirror. * 01-22:14:55 (3372) [INFO] To address this issue please refer to the below wiki article  * 01-22:14:55 (3372) [INFO]  * 01-22:14:55 (3372) [INFO] https://wiki.centos.org/yum-errors * 01-22:14:55 (3372) [INFO]  * 01-22:14:55 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 01-22:14:55 (3372) [INFO]  * 01-22:14:56 (3372) [INFO] https://mir01.syntis.net/epel/7/x86_64/repodata/b44834602c6e8b37fbae74fc3edcd51badc5e0ba897fe7c8588521cd67632974-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 01-22:14:56 (3372) [INFO] Trying other mirror. * 01-22:14:57 (3372) [INFO] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/b44834602c6e8b37fbae74fc3edcd51badc5e0ba897fe7c8588521cd67632974-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 01-22:14:57 (3372) [INFO] Trying other mirror. * 01-22:15:19 (3372) [INFO]  * 01-22:15:19 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 01-22:15:19 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:15:20 (3382) [INFO]  * 01-22:15:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:15:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:15:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:15:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-01_22:15:21_modified_for_AlmaLinux_8.json * 01-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:15: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.  * 01-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:15:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:15:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:15:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:15:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:15:45 (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-22:16:19 (2925) [INFO] Checking if your system is up to date:  * 02-22:16:19 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:16:19 (3362) [INFO]  * 02-22:16:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:16:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:16:20 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:16:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:16:20 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:16:20 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:16:20 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:16:21 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:16:21 (3382) [INFO]  * 02-22:16:21 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:16:21 (3362) [INFO]  * 02-22:16:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:16:22 (3372) [INFO] Determining fastest mirrors * 02-22:16:25 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:16:25 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:16:25 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:16:25 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 02-22:16:48 (3372) [INFO]  * 02-22:16:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 02-22:16:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:16:48 (3382) [INFO]  * 02-22:16:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:16:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:16:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:16:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:16:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-02_22:16:49_modified_for_AlmaLinux_8.json * 02-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:16: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.  * 02-22:16:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:20 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:22 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:15:06 (2925) [INFO] Checking if your system is up to date:  * 03-22:15:06 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:15:06 (3362) [INFO]  * 03-22:15:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:06 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:15:06 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:15:06 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:15:06 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:15:06 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:15:06 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:15:07 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:15:07 (3382) [INFO]  * 03-22:15:07 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:15:07 (3362) [INFO]  * 03-22:15:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:08 (3372) [INFO] Determining fastest mirrors * 03-22:15:11 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:15:11 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:15:11 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:15:11 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 03-22:15:35 (3372) [INFO]  * 03-22:15:35 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 03-22:15:35 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:15:35 (3382) [INFO]  * 03-22:15:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:15:35 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:15:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:15:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:15:36 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-03_22:15:36_modified_for_AlmaLinux_8.json * 03-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:15: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.  * 03-22:15:37 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:34 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:37 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:37 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:37 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14: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  * 04-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 04-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:15:12 (3362) [INFO]  * 04-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:15:13 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:15:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:15:13 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:15:13 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:15:13 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:15:13 (3382) [INFO]  * 04-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:15:13 (3362) [INFO]  * 04-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:14 (3372) [INFO] Determining fastest mirrors * 04-22:15:16 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:15:16 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:15:16 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:15:16 (3372) [INFO] * epel: lon.mirror.rackspace.com * 04-22:15:40 (3372) [INFO]  * 04-22:15:40 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 04-22:15:40 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:40 (3382) [INFO]  * 04-22:15:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:40 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-04_22:15:41_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15: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.  * 04-22:15:41 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:14: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  * 05-22:15:29 (2925) [INFO] Checking if your system is up to date:  * 05-22:15:29 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:15:29 (3362) [INFO]  * 05-22:15:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:15:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:15:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:15:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:15:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:15:30 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:15:30 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:15:30 (3382) [INFO]  * 05-22:15:30 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:15:30 (3362) [INFO]  * 05-22:15:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:30 (3372) [INFO] Determining fastest mirrors * 05-22:15:36 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:15:36 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:15:36 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:15:36 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 05-22:15:57 (3372) [INFO]  * 05-22:15:57 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 05-22:15:57 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:15:57 (3382) [INFO]  * 05-22:15:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:15:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:15:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:15:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:15:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-05_22:15:58_modified_for_AlmaLinux_8.json * 05-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:15: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.  * 05-22:15:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:15:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:15:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:15: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  * 06-22:15:37 (2925) [INFO] Checking if your system is up to date:  * 06-22:15:37 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:15:37 (3362) [INFO]  * 06-22:15:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:15:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:15:38 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:15:38 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:15:38 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:15:38 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:15:38 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:15:38 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:15:38 (3382) [INFO]  * 06-22:15:38 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:15:38 (3362) [INFO]  * 06-22:15:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:15:39 (3372) [INFO] Determining fastest mirrors * 06-22:15:42 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:15:42 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:15:42 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:15:42 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 06-22:16:04 (3372) [INFO]  * 06-22:16:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 06-22:16:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:16:05 (3382) [INFO]  * 06-22:16:05 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:16:05 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:16:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:16:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:16:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-06_22:16:06_modified_for_AlmaLinux_8.json * 06-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:16: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.  * 06-22:16:06 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:14:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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  * 07-22:14:51 (2925) [INFO] Checking if your system is up to date:  * 07-22:14:51 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:14:51 (3362) [INFO]  * 07-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:14:52 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:14:52 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:14:52 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:14:52 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:14:52 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:14:54 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:14:54 (3382) [INFO]  * 07-22:14:54 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:14:54 (3362) [INFO]  * 07-22:14:54 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:55 (3372) [INFO] Determining fastest mirrors * 07-22:14:57 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:14:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:14:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:14:57 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 07-22:15:21 (3372) [INFO]  * 07-22:15:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 07-22:15:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:15:21 (3382) [INFO]  * 07-22:15:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:15:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:15:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:15:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-07_22:15:22_modified_for_AlmaLinux_8.json * 07-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:15: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.  * 07-22:15:22 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:14:18 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:14:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:20 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:14: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  * 08-22:14:56 (2925) [INFO] Checking if your system is up to date:  * 08-22:14:56 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:14:56 (3362) [INFO]  * 08-22:14:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:14:56 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:14:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:14:56 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:14:56 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:14:56 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:14:56 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:14:56 (3382) [INFO]  * 08-22:14:56 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:14:56 (3362) [INFO]  * 08-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:57 (3372) [INFO] Determining fastest mirrors * 08-22:14:59 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:14:59 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:14:59 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:14:59 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 08-22:15:22 (3372) [INFO]  * 08-22:15:22 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 08-22:15:22 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:15:22 (3382) [INFO]  * 08-22:15:22 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:15:22 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:15:22 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:15:22 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:15:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-08_22:15:23_modified_for_AlmaLinux_8.json * 08-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:15: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.  * 08-22:15:23 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:14: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  * 09-22:14:37 (2925) [INFO] Checking if your system is up to date:  * 09-22:14:37 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:14:37 (3362) [INFO]  * 09-22:14:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:14:38 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:14:38 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:14:38 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:14:38 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:14:38 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:14:38 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:14:38 (3382) [INFO]  * 09-22:14:38 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:14:38 (3362) [INFO]  * 09-22:14:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:39 (3372) [INFO] Determining fastest mirrors * 09-22:14:41 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:14:41 (3372) [INFO] * epel: fedora.mirrorservice.org * 09-22:15:01 (3372) [INFO]  * 09-22:15:01 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 09-22:15:01 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:15:02 (3382) [INFO]  * 09-22:15:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:15:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:15:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:15:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:15:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-09_22:15:03_modified_for_AlmaLinux_8.json * 09-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:15: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.  * 09-22:15:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:14:39 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:41 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:14: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  * 10-22:14:52 (3076) [ERROR] yum appears to be unstable. Please address this before upgrading * 10-22:14:52 (3077) [ERROR] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/35ad412ac710c50c1f9eb20afbecf960315eb4340caf4166343937c4303b91ca-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/.  * 10-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** yum is not stable  * 10-22:14:52 (2925) [INFO] Checking if your system is up to date:  * 10-22:14:52 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:14:52 (3362) [INFO]  * 10-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:14:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:14:52 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:14:52 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:14:52 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:14:52 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:14:52 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:14:52 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:14:52 (3382) [INFO]  * 10-22:14:52 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:14:52 (3362) [INFO]  * 10-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:14:53 (3372) [INFO] Determining fastest mirrors * 10-22:14:55 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:14:55 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:14:55 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:14:55 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 10-22:14:58 (3372) [INFO] https://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/repodata/e6078e13823f3935f4271314cd557bb4e4535a51ac5e6414237748ae7d7691a5-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 10-22:14:58 (3372) [INFO] Trying other mirror. * 10-22:14:58 (3372) [INFO] To address this issue please refer to the below wiki article  * 10-22:14:58 (3372) [INFO]  * 10-22:14:58 (3372) [INFO] https://wiki.centos.org/yum-errors * 10-22:14:58 (3372) [INFO]  * 10-22:14:58 (3372) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 10-22:14:58 (3372) [INFO]  * 10-22:15:23 (3372) [INFO]  * 10-22:15:23 (3372) [INFO] kernel.x86_64 3.10.0-1160.76.1.el7 updates * 10-22:15:23 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:15:23 (3382) [INFO]  * 10-22:15:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:15:23 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:15:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:15:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:15:24 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-10_22:15:24_modified_for_AlmaLinux_8.json * 10-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:15: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.  * 10-22:15:24 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:15:22 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:15:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:15:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:15:23 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:15: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  * 11-22:15:55 (2925) [INFO] Checking if your system is up to date:  * 11-22:15:55 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:15:55 (3362) [INFO]  * 11-22:15:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:15:56 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:15:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:15:56 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:15:56 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:15:56 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:15:56 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:15:56 (3382) [INFO]  * 11-22:15:56 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:15:56 (3362) [INFO]  * 11-22:15:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:57 (3372) [INFO] Determining fastest mirrors * 11-22:16:01 (3372) [INFO] * EA4: 185.15.22.168 * 11-22:16:01 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 11-22:16:01 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 11-22:16:01 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 11-22:16:25 (3372) [INFO]  * 11-22:16:25 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 11-22:16:25 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-22:16:25 (3382) [INFO]  * 11-22:16:25 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:16:25 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:16:25 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:16:25 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:16:26 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-11_22:16:26_modified_for_AlmaLinux_8.json * 11-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:16: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-22:16:26 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:14: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  * 12-22:15:35 (2925) [INFO] Checking if your system is up to date:  * 12-22:15:35 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:15:35 (3362) [INFO]  * 12-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:15:35 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:15:35 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:15:35 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:15:35 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:15:35 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:15:35 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:15:35 (3382) [INFO]  * 12-22:15:35 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:15:35 (3362) [INFO]  * 12-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:36 (3372) [INFO] Determining fastest mirrors * 12-22:15:39 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:15:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:15:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:15:39 (3372) [INFO] * epel: mirror.freethought-internet.co.uk * 12-22:16:02 (3372) [INFO]  * 12-22:16:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 12-22:16:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:16:02 (3382) [INFO]  * 12-22:16:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:16:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:16:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:16:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:16:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-12_22:16:03_modified_for_AlmaLinux_8.json * 12-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:16: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.  * 12-22:16:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14: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  * 13-22:15:29 (2925) [INFO] Checking if your system is up to date:  * 13-22:15:29 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:15:29 (3362) [INFO]  * 13-22:15:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:15:29 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:15:29 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:15:29 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:15:29 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:15:29 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:15:29 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:15:29 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:15:29 (3382) [INFO]  * 13-22:15:29 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:15:29 (3362) [INFO]  * 13-22:15:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:15:30 (3372) [INFO] Determining fastest mirrors * 13-22:15:36 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:15:36 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:15:36 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:15:36 (3372) [INFO] * epel: fedora.mirrorservice.org * 13-22:15:57 (3372) [INFO]  * 13-22:15:57 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 13-22:15:57 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:15:57 (3382) [INFO]  * 13-22:15:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:15:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:15:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:15:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:15:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-13_22:15:58_modified_for_AlmaLinux_8.json * 13-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:15: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-22:15:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:16:46 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:16:47 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:16:47 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:16:47 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:16: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  * 14-22:17:28 (2925) [INFO] Checking if your system is up to date:  * 14-22:17:28 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:17:28 (3362) [INFO]  * 14-22:17:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:17:29 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:17:29 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:17:29 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:17:29 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:17:29 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:17:29 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:17:30 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:17:30 (3382) [INFO]  * 14-22:17:30 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:17:30 (3362) [INFO]  * 14-22:17:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:17:30 (3372) [INFO] Determining fastest mirrors * 14-22:17:33 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:17:33 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:17:33 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:17:33 (3372) [INFO] * epel: fedora.mirrorservice.org * 14-22:17:53 (3372) [INFO]  * 14-22:17:53 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 14-22:17:53 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:17:53 (3382) [INFO]  * 14-22:17:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:17:53 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:17:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:17:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:17:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-14_22:17:54_modified_for_AlmaLinux_8.json * 14-22:17: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:17: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.  * 14-22:17:54 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:14:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:14: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  * 15-22:14:55 (2925) [INFO] Checking if your system is up to date:  * 15-22:14:55 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:14:55 (3362) [INFO]  * 15-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:56 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:14:56 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:14:56 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:14:56 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:14:56 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:14:56 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:14:56 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:14:56 (3382) [INFO]  * 15-22:14:56 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:14:56 (3362) [INFO]  * 15-22:14:56 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:56 (3372) [INFO] Determining fastest mirrors * 15-22:14:58 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:14:58 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:14:58 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:14:58 (3372) [INFO] * epel: fedora.mirrorservice.org * 15-22:15:22 (3372) [INFO]  * 15-22:15:22 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 15-22:15:22 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:15:23 (3382) [INFO]  * 15-22:15:23 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:15:23 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:15:23 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:15:23 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:15:23 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-15_22:15:23_modified_for_AlmaLinux_8.json * 15-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:15: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.  * 15-22:15:24 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:14:23 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:26 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:14: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  * 16-22:15:00 (2925) [INFO] Checking if your system is up to date:  * 16-22:15:00 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:15:00 (3362) [INFO]  * 16-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:15:04 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:15:04 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:15:04 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:15:04 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:15:04 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:15:04 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:15:04 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:15:04 (3382) [INFO]  * 16-22:15:04 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:15:04 (3362) [INFO]  * 16-22:15:05 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:15:05 (3372) [INFO] Determining fastest mirrors * 16-22:15:10 (3372) [INFO] * EA4: 178.18.193.52 * 16-22:15:10 (3372) [INFO] * cpanel-addons-production-feed: 178.18.193.52 * 16-22:15:10 (3372) [INFO] * cpanel-plugins: 178.18.193.52 * 16-22:15:10 (3372) [INFO] * epel: lon.mirror.rackspace.com * 16-22:15:30 (3372) [INFO]  * 16-22:15:30 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 16-22:15:30 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:15:30 (3382) [INFO]  * 16-22:15:30 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:15:30 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:15:30 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:15:30 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:15:31 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-16_22:15:31_modified_for_AlmaLinux_8.json * 16-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:15: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.  * 16-22:15:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:14:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:14: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  * 17-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 17-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:14:57 (3362) [INFO]  * 17-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:14:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:14:58 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:14:58 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:14:58 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:14:58 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:14:58 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:14:58 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:14:58 (3382) [INFO]  * 17-22:14:58 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:14:58 (3362) [INFO]  * 17-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:14:58 (3372) [INFO] Determining fastest mirrors * 17-22:15:01 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:15:01 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:15:01 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:15:01 (3372) [INFO] * epel: lon.mirror.rackspace.com * 17-22:15:24 (3372) [INFO]  * 17-22:15:24 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 17-22:15:24 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:15:24 (3382) [INFO]  * 17-22:15:24 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:15:24 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:15:24 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:15:24 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:15:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-17_22:15:25_modified_for_AlmaLinux_8.json * 17-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:15: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.  * 17-22:15:25 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:14:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:14:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:20 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:20 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:14: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  * 18-22:14:51 (2925) [INFO] Checking if your system is up to date:  * 18-22:14:51 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:14:51 (3362) [INFO]  * 18-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:14:53 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:14:53 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:14:53 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:14:53 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:14:53 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:14:53 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:14:53 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:14:53 (3382) [INFO]  * 18-22:14:53 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:14:53 (3362) [INFO]  * 18-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:14:54 (3372) [INFO] Determining fastest mirrors * 18-22:14:57 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:14:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:14:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:14:57 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 18-22:15:24 (3372) [INFO]  * 18-22:15:24 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 18-22:15:24 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:15:24 (3382) [INFO]  * 18-22:15:24 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:15:24 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:15:24 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:15:24 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:15:25 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-18_22:15:25_modified_for_AlmaLinux_8.json * 18-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:15: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.  * 18-22:15:25 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:14:56 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:14: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  * 19-22:15:32 (2925) [INFO] Checking if your system is up to date:  * 19-22:15:32 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:15:32 (3362) [INFO]  * 19-22:15:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:15:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:15:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:15:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:15:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:15:32 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:15:33 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:15:33 (3382) [INFO]  * 19-22:15:33 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:15:33 (3362) [INFO]  * 19-22:15:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:33 (3372) [INFO] Determining fastest mirrors * 19-22:15:39 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:15:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:15:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:15:39 (3372) [INFO] * epel: lon.mirror.rackspace.com * 19-22:15:59 (3372) [INFO]  * 19-22:15:59 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 19-22:15:59 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:15:59 (3382) [INFO]  * 19-22:15:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:15:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:15:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:15:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:16:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-19_22:16:00_modified_for_AlmaLinux_8.json * 19-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:16: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.  * 19-22:16:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:15:16 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:15:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:15:19 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:15:19 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:15: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  * 20-22:15:50 (2925) [INFO] Checking if your system is up to date:  * 20-22:15:50 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:15:50 (3362) [INFO]  * 20-22:15:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:15:50 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:15:50 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:15:50 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:15:50 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:15:50 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:15:50 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:15:50 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:15:50 (3382) [INFO]  * 20-22:15:50 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:15:50 (3362) [INFO]  * 20-22:15:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:15:51 (3372) [INFO] Determining fastest mirrors * 20-22:15:56 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:15:56 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:15:56 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:15:56 (3372) [INFO] * epel: lon.mirror.rackspace.com * 20-22:16:18 (3372) [INFO]  * 20-22:16:18 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 20-22:16:18 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:16:18 (3382) [INFO]  * 20-22:16:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:16:18 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:16:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:16:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:16:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-20_22:16:19_modified_for_AlmaLinux_8.json * 20-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:16: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.  * 20-22:16:20 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:14:34 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:14:36 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:36 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:36 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:14: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  * 21-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 21-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:15:13 (3362) [INFO]  * 21-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:15:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:15:14 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:15:14 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:15:14 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:15:14 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:15:14 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:15:14 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:15:14 (3382) [INFO]  * 21-22:15:14 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:15:14 (3362) [INFO]  * 21-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:15:15 (3372) [INFO] Determining fastest mirrors * 21-22:15:20 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:15:20 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:15:20 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:15:20 (3372) [INFO] * epel: mirrors.20i.com * 21-22:15:43 (3372) [INFO]  * 21-22:15:43 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 21-22:15:43 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:15:43 (3382) [INFO]  * 21-22:15:43 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:15:43 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:15:43 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:15:43 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:15:44 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-21_22:15:44_modified_for_AlmaLinux_8.json * 21-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:15: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.  * 21-22:15:44 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:14:22 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:14:24 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:24 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:24 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:14:24 (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-22:15:08 (2925) [INFO] Checking if your system is up to date:  * 22-22:15:08 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:15:08 (3362) [INFO]  * 22-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:15:09 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:15:09 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:15:09 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:15:09 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:15:09 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:15:09 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:15:09 (3382) [INFO]  * 22-22:15:09 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:15:09 (3362) [INFO]  * 22-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:10 (3372) [INFO] Determining fastest mirrors * 22-22:15:18 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:15:18 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:15:18 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:15:18 (3372) [INFO] * epel: mirrors.20i.com * 22-22:15:40 (3372) [INFO]  * 22-22:15:40 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 22-22:15:40 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:15:40 (3382) [INFO]  * 22-22:15:40 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:15:40 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:15:40 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:15:40 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:15:41 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-22_22:15:41_modified_for_AlmaLinux_8.json * 22-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:15: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.  * 22-22:15:41 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:14:12 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:14:15 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:15 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:15 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:14: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  * 23-22:14:54 (2925) [INFO] Checking if your system is up to date:  * 23-22:14:54 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:14:55 (3362) [INFO]  * 23-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:14:55 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:14:55 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:14:55 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:14:55 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:14:55 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:14:55 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:14:55 (3382) [INFO]  * 23-22:14:55 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:14:55 (3362) [INFO]  * 23-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:56 (3372) [INFO] Determining fastest mirrors * 23-22:14:57 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:14:57 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:14:57 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:14:57 (3372) [INFO] * epel: mirrors.20i.com * 23-22:15:21 (3372) [INFO]  * 23-22:15:21 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 23-22:15:21 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:15:21 (3382) [INFO]  * 23-22:15:21 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:15:21 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:15:21 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:15:22 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-23_22:15:22_modified_for_AlmaLinux_8.json * 23-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:15: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.  * 23-22:15:22 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:14:20 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:14:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:22 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:14: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  * 24-22:14:50 (2925) [INFO] Checking if your system is up to date:  * 24-22:14:50 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:14:50 (3362) [INFO]  * 24-22:14:50 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:50 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:14:50 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:14:50 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:14:50 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:14:50 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:14:50 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:14:51 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:14:51 (3382) [INFO]  * 24-22:14:51 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:14:51 (3362) [INFO]  * 24-22:14:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:51 (3372) [INFO] Determining fastest mirrors * 24-22:14:53 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:14:53 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:14:53 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:14:53 (3372) [INFO] * epel: mirrors.20i.com * 24-22:15:18 (3372) [INFO]  * 24-22:15:18 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 24-22:15:18 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:15:18 (3382) [INFO]  * 24-22:15:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:15:18 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:15:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:15:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:15:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-24_22:15:19_modified_for_AlmaLinux_8.json * 24-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:15: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.  * 24-22:15:19 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:13:54 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:13:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:13:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:13:56 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:13: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  * 25-22:14:22 (2925) [INFO] Checking if your system is up to date:  * 25-22:14:22 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:14:22 (3362) [INFO]  * 25-22:14:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:14:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:14:22 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:14:22 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:14:22 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:14:22 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:14:22 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:14:23 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:14:23 (3382) [INFO]  * 25-22:14:23 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:14:23 (3362) [INFO]  * 25-22:14:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:14:23 (3372) [INFO] Determining fastest mirrors * 25-22:14:25 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:14:25 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:14:25 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:14:25 (3372) [INFO] * epel: lon.mirror.rackspace.com * 25-22:14:44 (3372) [INFO]  * 25-22:14:44 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 25-22:14:44 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:14:44 (3382) [INFO]  * 25-22:14:44 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:14:44 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:14:44 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:14:45 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-25_22:14:45_modified_for_AlmaLinux_8.json * 25-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:14: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.  * 25-22:14:45 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:14:40 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:41 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:14: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  * 26-22:15:07 (2925) [INFO] Checking if your system is up to date:  * 26-22:15:07 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:15:07 (3362) [INFO]  * 26-22:15:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:08 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:15:08 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:15:08 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:15:08 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:15:08 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:15:08 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:15:08 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:15:08 (3382) [INFO]  * 26-22:15:08 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:15:08 (3362) [INFO]  * 26-22:15:08 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:08 (3372) [INFO] Determining fastest mirrors * 26-22:15:14 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:15:14 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:15:14 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:15:14 (3372) [INFO] * epel: mirrors.20i.com * 26-22:15:32 (3372) [INFO]  * 26-22:15:32 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 26-22:15:32 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:15:32 (3382) [INFO]  * 26-22:15:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:15:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:15:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:15:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:15:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-26_22:15:33_modified_for_AlmaLinux_8.json * 26-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:15: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.  * 26-22:15:33 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:45 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14: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  * 27-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 27-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:15:13 (3362) [INFO]  * 27-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:15:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:15:13 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:15:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:15:13 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:15:13 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:15:13 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:15:13 (3382) [INFO]  * 27-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:15:13 (3362) [INFO]  * 27-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:15:14 (3372) [INFO] Determining fastest mirrors * 27-22:15:18 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:15:18 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:15:18 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:15:18 (3372) [INFO] * epel: mirrors.20i.com * 27-22:15:37 (3372) [INFO]  * 27-22:15:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 27-22:15:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:15:37 (3382) [INFO]  * 27-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-27_22:15:37_modified_for_AlmaLinux_8.json * 27-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:15: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.  * 27-22:15:38 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:14:35 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:14:36 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:36 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:36 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:14: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  * 28-22:15:02 (2925) [INFO] Checking if your system is up to date:  * 28-22:15:02 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:15:02 (3362) [INFO]  * 28-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:03 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:15:03 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:15:03 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:15:03 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:15:03 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:15:03 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:15:03 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:15:03 (3382) [INFO]  * 28-22:15:03 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:15:03 (3362) [INFO]  * 28-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:04 (3372) [INFO] Determining fastest mirrors * 28-22:15:09 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:15:09 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:15:09 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:15:09 (3372) [INFO] * epel: mirrors.20i.com * 28-22:15:52 (3372) [INFO]  * 28-22:15:52 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 28-22:15:52 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:15:52 (3382) [INFO]  * 28-22:15:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:15:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:15:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:15:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:15:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-28_22:15:53_modified_for_AlmaLinux_8.json * 28-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:15: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.  * 28-22:15:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-22:13:58 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 29-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:13:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 29-22:13: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  * 29-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 29-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 29-22:14:26 (3362) [INFO]  * 29-22:14:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 29-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 29-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 29-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 29-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 29-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 29-22:14:27 (3382) [INFO]  * 29-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 29-22:14:27 (3362) [INFO]  * 29-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:14:27 (3372) [INFO] Determining fastest mirrors * 29-22:14:31 (3372) [INFO] * EA4: 185.15.22.168 * 29-22:14:31 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 29-22:14:31 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 29-22:14:31 (3372) [INFO] * epel: lon.mirror.rackspace.com * 29-22:14:49 (3372) [INFO]  * 29-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 29-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-22:14:49 (3382) [INFO]  * 29-22:14:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-22:14:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-22:14:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-22:14:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-22:14:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-29_22:14:49_modified_for_AlmaLinux_8.json * 29-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 29-22:14: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.  * 29-22:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-22:14:03 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 30-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 30-22:14: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  * 30-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 30-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 30-22:14:32 (3362) [INFO]  * 30-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 30-22:14:33 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-22:14:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 30-22:14:33 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 30-22:14:33 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 30-22:14:33 (3372) [INFO] : wp-toolkit-thirdparties * 30-22:14:33 (3372) [INFO] Cleaning up list of fastest mirrors * 30-22:14:33 (3382) [INFO]  * 30-22:14:33 (3361) [INFO] Running: /usr/bin/yum check-update * 30-22:14:33 (3362) [INFO]  * 30-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:33 (3372) [INFO] Determining fastest mirrors * 30-22:14:37 (3372) [INFO] * EA4: 185.15.22.168 * 30-22:14:37 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 30-22:14:37 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 30-22:14:37 (3372) [INFO] * epel: mirrors.20i.com * 30-22:14:54 (3372) [INFO]  * 30-22:14:54 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 30-22:14:54 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-22:14:54 (3382) [INFO]  * 30-22:14:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-22:14:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-22:14:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-22:14:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-11-30_22:14:55_modified_for_AlmaLinux_8.json * 30-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 30-22:14: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.  * 30-22:14:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:15:06 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:15:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:15:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:15:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:15: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  * 01-22:15:36 (2925) [INFO] Checking if your system is up to date:  * 01-22:15:36 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:15:36 (3362) [INFO]  * 01-22:15:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:15:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:15:36 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:15:36 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:15:36 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:15:36 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:15:36 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:15:36 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:15:36 (3382) [INFO]  * 01-22:15:36 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:15:36 (3362) [INFO]  * 01-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:15:37 (3372) [INFO] Determining fastest mirrors * 01-22:15:42 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:15:42 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:15:42 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:15:42 (3372) [INFO] * epel: lon.mirror.rackspace.com * 01-22:15:59 (3372) [INFO]  * 01-22:15:59 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 01-22:15:59 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:15:59 (3382) [INFO]  * 01-22:15:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:15:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:15:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:15:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:16:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-01_22:16:00_modified_for_AlmaLinux_8.json * 01-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:16: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.  * 01-22:16:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:13:59 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:01 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:14: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  * 02-22:14:24 (2925) [INFO] Checking if your system is up to date:  * 02-22:14:24 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:14:24 (3362) [INFO]  * 02-22:14:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:14:24 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:14:24 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:14:24 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:14:24 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:14:24 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:14:25 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:14:25 (3382) [INFO]  * 02-22:14:25 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:14:25 (3362) [INFO]  * 02-22:14:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:25 (3372) [INFO] Determining fastest mirrors * 02-22:14:27 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:14:27 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:14:27 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:14:27 (3372) [INFO] * epel: lon.mirror.rackspace.com * 02-22:14:46 (3372) [INFO]  * 02-22:14:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 02-22:14:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:14:46 (3382) [INFO]  * 02-22:14:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:14:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:14:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:14:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:14:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-02_22:14:47_modified_for_AlmaLinux_8.json * 02-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:14: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-22:14:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:49 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:15:21 (2925) [INFO] Checking if your system is up to date:  * 03-22:15:21 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:15:21 (3362) [INFO]  * 03-22:15:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:15:21 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:15:21 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:15:21 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:15:21 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:15:21 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:15:22 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:15:22 (3382) [INFO]  * 03-22:15:22 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:15:22 (3362) [INFO]  * 03-22:15:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:15:23 (3372) [INFO] Determining fastest mirrors * 03-22:15:26 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:15:26 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:15:26 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:15:26 (3372) [INFO] * epel: mirrors.20i.com * 03-22:15:46 (3372) [INFO]  * 03-22:15:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 03-22:15:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:15:46 (3382) [INFO]  * 03-22:15:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:15:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:15:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:15:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:15:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-03_22:15:47_modified_for_AlmaLinux_8.json * 03-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:15: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.  * 03-22:15:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:46 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:48 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14: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  * 04-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 04-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:15:13 (3362) [INFO]  * 04-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:15:13 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:15:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:15:13 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:15:13 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:15:13 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:15:13 (3382) [INFO]  * 04-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:15:13 (3362) [INFO]  * 04-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:14 (3372) [INFO] Determining fastest mirrors * 04-22:15:19 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * epel: mirrors.20i.com * 04-22:15:36 (3372) [INFO]  * 04-22:15:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 04-22:15:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:36 (3382) [INFO]  * 04-22:15:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:36 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-04_22:15:37_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15: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.  * 04-22:15:37 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:14:10 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:14:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:12 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:12 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:14:12 (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-22:14:39 (2925) [INFO] Checking if your system is up to date:  * 05-22:14:39 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:14:39 (3362) [INFO]  * 05-22:14:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:14:39 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:14:39 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:14:39 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:14:39 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:14:39 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:14:39 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:14:39 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:14:39 (3382) [INFO]  * 05-22:14:39 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:14:39 (3362) [INFO]  * 05-22:14:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:14:40 (3372) [INFO] Determining fastest mirrors * 05-22:14:42 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:14:42 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:14:42 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:14:42 (3372) [INFO] * epel: mirrors.20i.com * 05-22:14:59 (3372) [INFO]  * 05-22:14:59 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 05-22:14:59 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:14:59 (3382) [INFO]  * 05-22:14:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:14:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:14:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:14:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:15:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-05_22:15:00_modified_for_AlmaLinux_8.json * 05-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:15: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.  * 05-22:15:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:14:04 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:06 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:14: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  * 06-22:14:30 (2925) [INFO] Checking if your system is up to date:  * 06-22:14:30 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:14:30 (3362) [INFO]  * 06-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:31 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:14:31 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:14:31 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:14:31 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:14:31 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:14:31 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:14:31 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:14:31 (3382) [INFO]  * 06-22:14:31 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:14:31 (3362) [INFO]  * 06-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:31 (3372) [INFO] Determining fastest mirrors * 06-22:14:36 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:14:36 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:14:36 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:14:36 (3372) [INFO] * epel: lon.mirror.rackspace.com * 06-22:14:53 (3372) [INFO]  * 06-22:14:53 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 06-22:14:53 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:14:54 (3382) [INFO]  * 06-22:14:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:14:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:14:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:14:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-06_22:14:54_modified_for_AlmaLinux_8.json * 06-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:14: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.  * 06-22:14:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:14:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:17 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:17 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:17 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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-22:15:11 (2925) [INFO] Checking if your system is up to date:  * 07-22:15:11 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:15:11 (3362) [INFO]  * 07-22:15:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:15:11 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:15:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:15:11 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:15:11 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:15:11 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:15:12 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:15:12 (3382) [INFO]  * 07-22:15:12 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:15:12 (3362) [INFO]  * 07-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:12 (3372) [INFO] Determining fastest mirrors * 07-22:15:26 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:15:26 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:15:26 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:15:26 (3372) [INFO] * epel: lon.mirror.rackspace.com * 07-22:15:58 (3372) [INFO]  * 07-22:15:58 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 07-22:15:58 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:15:58 (3382) [INFO]  * 07-22:15:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:15:58 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:15:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:15:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:15:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-07_22:15:59_modified_for_AlmaLinux_8.json * 07-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:15: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.  * 07-22:15:59 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:15:55 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:15:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:15:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:15:56 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:15: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-22:16:19 (2925) [INFO] Checking if your system is up to date:  * 08-22:16:19 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:16:19 (3362) [INFO]  * 08-22:16:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:16:21 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:16:21 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:16:21 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:16:21 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:16:21 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:16:21 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:16:22 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:16:22 (3382) [INFO]  * 08-22:16:22 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:16:22 (3362) [INFO]  * 08-22:16:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:16:22 (3372) [INFO] Determining fastest mirrors * 08-22:16:27 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:16:27 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:16:27 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:16:27 (3372) [INFO] * epel: lon.mirror.rackspace.com * 08-22:16:46 (3372) [INFO]  * 08-22:16:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 08-22:16:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:16:46 (3382) [INFO]  * 08-22:16:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:16:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:16:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:16:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:16:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-08_22:16:47_modified_for_AlmaLinux_8.json * 08-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:16: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.  * 08-22:16:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:13:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:14:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:00 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:14: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  * 09-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 09-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:14:26 (3362) [INFO]  * 09-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:14:27 (3382) [INFO]  * 09-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:14:27 (3362) [INFO]  * 09-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:27 (3372) [INFO] Determining fastest mirrors * 09-22:14:31 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:14:31 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:14:31 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:14:31 (3372) [INFO] * epel: mirrors.20i.com * 09-22:14:48 (3372) [INFO]  * 09-22:14:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 09-22:14:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:14:48 (3382) [INFO]  * 09-22:14:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:14:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:14:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:14:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:14:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-09_22:14:49_modified_for_AlmaLinux_8.json * 09-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:14: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.  * 09-22:14:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:14:43 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:14:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:14:45 (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-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 10-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:15:12 (3362) [INFO]  * 10-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:15:12 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:15:12 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:15:12 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:15:12 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:15:12 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:15:13 (3382) [INFO]  * 10-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:15:13 (3362) [INFO]  * 10-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:13 (3372) [INFO] Determining fastest mirrors * 10-22:15:19 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:15:19 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:15:19 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:15:19 (3372) [INFO] * epel: lon.mirror.rackspace.com * 10-22:15:36 (3372) [INFO]  * 10-22:15:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 10-22:15:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:15:36 (3382) [INFO]  * 10-22:15:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:15:36 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:15:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:15:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-10_22:15:37_modified_for_AlmaLinux_8.json * 10-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:15: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.  * 10-22:15:37 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:14:45 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:48 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:14: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  * 11-22:15:17 (2925) [INFO] Checking if your system is up to date:  * 11-22:15:17 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:15:17 (3362) [INFO]  * 11-22:15:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:17 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:15:17 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:15:17 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:15:17 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:15:17 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:15:17 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:15:17 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:15:17 (3382) [INFO]  * 11-22:15:17 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:15:17 (3362) [INFO]  * 11-22:15:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:18 (3372) [INFO] Determining fastest mirrors * 11-22:15:59 (3372) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was * 11-22:15:59 (3372) [INFO] 12: Timeout on http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] One of the configured repositories failed (Unknown), * 11-22:15:59 (3372) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 11-22:15:59 (3372) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 11-22:15:59 (3372) [INFO] upstream. This is most often useful if you are using a newer * 11-22:15:59 (3372) [INFO] distribution release than is supported by the repository (and the * 11-22:15:59 (3372) [INFO] packages for the previous distribution release still work). * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] 3. Run the command with the repository temporarily disabled * 11-22:15:59 (3372) [INFO] yum --disablerepo= ... * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 11-22:15:59 (3372) [INFO] will then just ignore the repository until you permanently enable it * 11-22:15:59 (3372) [INFO] again or use --enablerepo for temporary usage: * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] yum-config-manager --disable  * 11-22:15:59 (3372) [INFO] or * 11-22:15:59 (3372) [INFO] subscription-manager repos --disable= * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 11-22:15:59 (3372) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 11-22:15:59 (3372) [INFO] so will have to try and fail each time (and thus. yum will be be much * 11-22:15:59 (3372) [INFO] slower). If it is a very temporary problem though, this is often a nice * 11-22:15:59 (3372) [INFO] compromise: * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 11-22:15:59 (3372) [INFO]  * 11-22:15:59 (3372) [INFO] Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64 * 11-22:15:59 (3382) [INFO]  * 11-22:15:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:15:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:15:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:15:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:16:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-11_22:16:18_modified_for_AlmaLinux_8.json * 11-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:16: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.  * 11-22:16:18 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:14:29 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:31 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:31 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:14: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  * 12-22:14:52 (2925) [INFO] Checking if your system is up to date:  * 12-22:14:52 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:14:52 (3362) [INFO]  * 12-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:52 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:14:52 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:14:52 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:14:52 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:14:52 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:14:52 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:14:52 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:14:52 (3382) [INFO]  * 12-22:14:52 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:14:52 (3362) [INFO]  * 12-22:14:53 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:53 (3372) [INFO] Determining fastest mirrors * 12-22:14:56 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:14:56 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:14:56 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:14:56 (3372) [INFO] * epel: mirrors.20i.com * 12-22:15:18 (3372) [INFO]  * 12-22:15:18 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 12-22:15:18 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:15:18 (3382) [INFO]  * 12-22:15:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:15:18 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:15:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:15:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:15:19 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-12_22:15:19_modified_for_AlmaLinux_8.json * 12-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:15: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.  * 12-22:15:19 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:05 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14: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  * 13-22:14:30 (2925) [INFO] Checking if your system is up to date:  * 13-22:14:30 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:14:30 (3362) [INFO]  * 13-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:14:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:14:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:14:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:14:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:14:30 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:14:30 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:14:30 (3382) [INFO]  * 13-22:14:30 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:14:30 (3362) [INFO]  * 13-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:30 (3372) [INFO] Determining fastest mirrors * 13-22:14:34 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * epel: lon.mirror.rackspace.com * 13-22:14:51 (3372) [INFO]  * 13-22:14:51 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 13-22:14:51 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:14:51 (3382) [INFO]  * 13-22:14:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:14:51 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:14:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:14:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:14:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-13_22:14:52_modified_for_AlmaLinux_8.json * 13-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:14:52 (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-22:14:52 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:14:58 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:58 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:58 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:14: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  * 14-22:15:24 (2925) [INFO] Checking if your system is up to date:  * 14-22:15:24 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:15:24 (3362) [INFO]  * 14-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:15:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:15:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:15:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:15:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:15:25 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:15:25 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:15:25 (3382) [INFO]  * 14-22:15:25 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:15:25 (3362) [INFO]  * 14-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:25 (3372) [INFO] Determining fastest mirrors * 14-22:15:31 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:15:31 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:15:31 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:15:31 (3372) [INFO] * epel: lon.mirror.rackspace.com * 14-22:15:48 (3372) [INFO]  * 14-22:15:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 14-22:15:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:15:48 (3382) [INFO]  * 14-22:15:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:15:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:15:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:15:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:15:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-14_22:15:49_modified_for_AlmaLinux_8.json * 14-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:15: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.  * 14-22:15:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:14:08 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:14: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  * 15-22:14:31 (2925) [INFO] Checking if your system is up to date:  * 15-22:14:31 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:14:31 (3362) [INFO]  * 15-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:14:32 (3382) [INFO]  * 15-22:14:32 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:14:32 (3362) [INFO]  * 15-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:32 (3372) [INFO] Determining fastest mirrors * 15-22:14:37 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:14:37 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:14:37 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:14:37 (3372) [INFO] * epel: mirrors.20i.com * 15-22:14:53 (3372) [INFO]  * 15-22:14:53 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 15-22:14:53 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:14:54 (3382) [INFO]  * 15-22:14:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:14:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:14:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:14:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-15_22:14:54_modified_for_AlmaLinux_8.json * 15-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:14: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.  * 15-22:14:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:14:01 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:14: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  * 16-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 16-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:14:26 (3362) [INFO]  * 16-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:14:27 (3382) [INFO]  * 16-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:14:27 (3362) [INFO]  * 16-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:27 (3372) [INFO] Determining fastest mirrors * 16-22:14:30 (3372) [INFO] * EA4: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * epel: mirrors.20i.com * 16-22:14:47 (3372) [INFO]  * 16-22:14:47 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 16-22:14:47 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:14:47 (3382) [INFO]  * 16-22:14:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:14:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:14:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:14:48 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-16_22:14:48_modified_for_AlmaLinux_8.json * 16-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:14: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.  * 16-22:14:48 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:14:49 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:14: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  * 17-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 17-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:15:13 (3362) [INFO]  * 17-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:15:14 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:15:14 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:15:14 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:15:14 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:15:14 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:15:14 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:15:14 (3382) [INFO]  * 17-22:15:14 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:15:14 (3362) [INFO]  * 17-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:14 (3372) [INFO] Determining fastest mirrors * 17-22:15:17 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:15:17 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:15:17 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:15:17 (3372) [INFO] * epel: mirrors.20i.com * 17-22:15:35 (3372) [INFO]  * 17-22:15:35 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 17-22:15:35 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:15:35 (3382) [INFO]  * 17-22:15:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:15:35 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:15:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:15:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:15:36 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-17_22:15:36_modified_for_AlmaLinux_8.json * 17-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:15: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.  * 17-22:15:36 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:14:45 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:14:47 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:47 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:47 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:14: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  * 18-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 18-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:15:12 (3362) [INFO]  * 18-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:15:12 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:15:12 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:15:12 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:15:12 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:15:12 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:15:13 (3382) [INFO]  * 18-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:15:13 (3362) [INFO]  * 18-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:14 (3372) [INFO] Determining fastest mirrors * 18-22:15:17 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:15:17 (3372) [INFO] * epel: mirrors.20i.com * 18-22:15:34 (3372) [INFO]  * 18-22:15:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 18-22:15:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:15:34 (3382) [INFO]  * 18-22:15:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:15:34 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:15:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:15:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:15:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-18_22:15:35_modified_for_AlmaLinux_8.json * 18-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:15: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.  * 18-22:15:35 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:13:54 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:13:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:13:56 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:13:56 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:13: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-22:14:20 (2925) [INFO] Checking if your system is up to date:  * 19-22:14:20 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:14:20 (3362) [INFO]  * 19-22:14:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:14:20 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:14:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:14:20 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:14:20 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:14:20 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:14:20 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:14:20 (3382) [INFO]  * 19-22:14:20 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:14:20 (3362) [INFO]  * 19-22:14:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:14:21 (3372) [INFO] Determining fastest mirrors * 19-22:14:24 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:14:24 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:14:24 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:14:24 (3372) [INFO] * epel: lon.mirror.rackspace.com * 19-22:14:41 (3372) [INFO]  * 19-22:14:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.80.1.el7 updates * 19-22:14:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:14:41 (3382) [INFO]  * 19-22:14:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:14:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:14:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:14:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:14:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-19_22:14:42_modified_for_AlmaLinux_8.json * 19-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:14: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.  * 19-22:14:42 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:14:22 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:14:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:23 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:23 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:14: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  * 20-22:14:48 (2925) [INFO] Checking if your system is up to date:  * 20-22:14:48 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:14:48 (3362) [INFO]  * 20-22:14:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:14:49 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:14:49 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:14:49 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:14:49 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:14:49 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:14:49 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:14:49 (3382) [INFO]  * 20-22:14:49 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:14:49 (3362) [INFO]  * 20-22:14:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:49 (3372) [INFO] Determining fastest mirrors * 20-22:14:53 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:14:53 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:14:53 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:14:53 (3372) [INFO] * epel: lon.mirror.rackspace.com * 20-22:15:13 (3372) [INFO]  * 20-22:15:13 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 20-22:15:13 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:15:13 (3382) [INFO]  * 20-22:15:13 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:15:13 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:15:13 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:15:13 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:15:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-20_22:15:14_modified_for_AlmaLinux_8.json * 20-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:15: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-22:15:14 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:14:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:02 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:14:02 (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-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 21-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:14:26 (3362) [INFO]  * 21-22:14:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:14:27 (3382) [INFO]  * 21-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:14:27 (3362) [INFO]  * 21-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:27 (3372) [INFO] Determining fastest mirrors * 21-22:14:30 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:14:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:14:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:14:30 (3372) [INFO] * epel: mirrors.20i.com * 21-22:14:49 (3372) [INFO]  * 21-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 21-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:14:49 (3382) [INFO]  * 21-22:14:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:14:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:14:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:14:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-21_22:14:50_modified_for_AlmaLinux_8.json * 21-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:14: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.  * 21-22:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:15:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:21 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:15: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  * 22-22:15:44 (2925) [INFO] Checking if your system is up to date:  * 22-22:15:44 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:15:44 (3362) [INFO]  * 22-22:15:44 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:44 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:15:44 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:15:44 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:15:44 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:15:44 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:15:44 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:15:45 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:15:45 (3382) [INFO]  * 22-22:15:45 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:15:45 (3362) [INFO]  * 22-22:15:45 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:45 (3372) [INFO] Determining fastest mirrors * 22-22:15:50 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:15:50 (3372) [INFO] * epel: lon.mirror.rackspace.com * 22-22:16:09 (3372) [INFO]  * 22-22:16:09 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 22-22:16:09 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:16:09 (3382) [INFO]  * 22-22:16:09 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:16:09 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:16:09 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:16:09 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:16:10 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-22_22:16:10_modified_for_AlmaLinux_8.json * 22-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:16: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.  * 22-22:16:10 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:14:03 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:05 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:14:05 (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-22:14:28 (2925) [INFO] Checking if your system is up to date:  * 23-22:14:28 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:14:28 (3362) [INFO]  * 23-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:14:28 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:14:28 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:14:28 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:14:28 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:14:28 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:14:28 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:14:28 (3382) [INFO]  * 23-22:14:28 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:14:28 (3362) [INFO]  * 23-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:29 (3372) [INFO] Determining fastest mirrors * 23-22:14:33 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:14:33 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:14:33 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:14:33 (3372) [INFO] * epel: lon.mirror.rackspace.com * 23-22:14:51 (3372) [INFO]  * 23-22:14:51 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 23-22:14:51 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:14:51 (3382) [INFO]  * 23-22:14:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:14:51 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:14:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:14:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:14:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-23_22:14:52_modified_for_AlmaLinux_8.json * 23-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:14:52 (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-22:14:52 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:48 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:14: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-22:15:14 (2925) [INFO] Checking if your system is up to date:  * 24-22:15:14 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:15:14 (3362) [INFO]  * 24-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:15:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:15:14 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:15:14 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:15:14 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:15:14 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:15:14 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:15:14 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:15:14 (3382) [INFO]  * 24-22:15:14 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:15:14 (3362) [INFO]  * 24-22:15:15 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:15:15 (3372) [INFO] Determining fastest mirrors * 24-22:15:20 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:15:20 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:15:20 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:15:20 (3372) [INFO] * epel: lon.mirror.rackspace.com * 24-22:15:37 (3372) [INFO]  * 24-22:15:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 24-22:15:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:15:37 (3382) [INFO]  * 24-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:15:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-24_22:15:38_modified_for_AlmaLinux_8.json * 24-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:15: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.  * 24-22:15:38 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:14: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  * 25-22:15:10 (2925) [INFO] Checking if your system is up to date:  * 25-22:15:10 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:15:10 (3362) [INFO]  * 25-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:15:10 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:15:10 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:15:10 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:15:10 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:15:10 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:15:10 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:15:10 (3382) [INFO]  * 25-22:15:10 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:15:10 (3362) [INFO]  * 25-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:11 (3372) [INFO] Determining fastest mirrors * 25-22:15:16 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:15:16 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:15:16 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:15:16 (3372) [INFO] * epel: lon.mirror.rackspace.com * 25-22:15:32 (3372) [INFO]  * 25-22:15:32 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 25-22:15:32 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:15:33 (3382) [INFO]  * 25-22:15:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:15:33 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:15:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:15:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:15:33 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-25_22:15:33_modified_for_AlmaLinux_8.json * 25-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:15: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.  * 25-22:15:33 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:14:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:14: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-22:14:27 (2925) [INFO] Checking if your system is up to date:  * 26-22:14:27 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:14:27 (3362) [INFO]  * 26-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:14:27 (3382) [INFO]  * 26-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:14:27 (3362) [INFO]  * 26-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:28 (3372) [INFO] Determining fastest mirrors * 26-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:14:32 (3372) [INFO] * epel: lon.mirror.rackspace.com * 26-22:14:50 (3372) [INFO]  * 26-22:14:50 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 26-22:14:50 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:14:50 (3382) [INFO]  * 26-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:14:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:14:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:14:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-26_22:14:51_modified_for_AlmaLinux_8.json * 26-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:14: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.  * 26-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14: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  * 27-22:14:35 (2925) [INFO] Checking if your system is up to date:  * 27-22:14:35 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:14:35 (3362) [INFO]  * 27-22:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:14:35 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:14:35 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:14:35 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:14:35 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:14:35 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:14:35 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:14:35 (3382) [INFO]  * 27-22:14:35 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:14:35 (3362) [INFO]  * 27-22:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:36 (3372) [INFO] Determining fastest mirrors * 27-22:14:39 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:14:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:14:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:14:39 (3372) [INFO] * epel: mirrors.20i.com * 27-22:14:56 (3372) [INFO]  * 27-22:14:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 27-22:14:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:14:56 (3382) [INFO]  * 27-22:14:56 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:14:56 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:14:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:14:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:14:57 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-27_22:14:57_modified_for_AlmaLinux_8.json * 27-22:14:57 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:14:57 (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-22:14:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:14:01 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:14: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  * 28-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 28-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:14:26 (3362) [INFO]  * 28-22:14:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:14:26 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:14:26 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:14:26 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:14:26 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:14:26 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:14:26 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:14:26 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:14:26 (3382) [INFO]  * 28-22:14:26 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:14:26 (3362) [INFO]  * 28-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:14:27 (3372) [INFO] Determining fastest mirrors * 28-22:14:31 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:14:31 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:14:31 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:14:31 (3372) [INFO] * epel: lon.mirror.rackspace.com * 28-22:14:49 (3372) [INFO]  * 28-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 28-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:14:49 (3382) [INFO]  * 28-22:14:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:14:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:14:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:14:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-28_22:14:50_modified_for_AlmaLinux_8.json * 28-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:14: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-22:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-22:14:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 29-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 29-22:14: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-22:14:30 (2925) [INFO] Checking if your system is up to date:  * 29-22:14:30 (3361) [INFO] Running: /usr/bin/yum clean all * 29-22:14:30 (3362) [INFO]  * 29-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:14:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 29-22:14:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-22:14:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 29-22:14:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 29-22:14:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 29-22:14:30 (3372) [INFO] : wp-toolkit-thirdparties * 29-22:14:31 (3372) [INFO] Cleaning up list of fastest mirrors * 29-22:14:31 (3382) [INFO]  * 29-22:14:31 (3361) [INFO] Running: /usr/bin/yum check-update * 29-22:14:31 (3362) [INFO]  * 29-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:14:31 (3372) [INFO] Determining fastest mirrors * 29-22:14:34 (3372) [INFO] * EA4: 185.15.22.168 * 29-22:14:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 29-22:14:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 29-22:14:34 (3372) [INFO] * epel: lon.mirror.rackspace.com * 29-22:14:52 (3372) [INFO]  * 29-22:14:52 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 29-22:14:52 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-22:14:52 (3382) [INFO]  * 29-22:14:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-22:14:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-22:14:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-22:14:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-29_22:14:53_modified_for_AlmaLinux_8.json * 29-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 29-22:14: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-22:14:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-22:14:01 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 30-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:06 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 30-22:14: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-22:14:30 (2925) [INFO] Checking if your system is up to date:  * 30-22:14:30 (3361) [INFO] Running: /usr/bin/yum clean all * 30-22:14:30 (3362) [INFO]  * 30-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 30-22:14:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-22:14:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 30-22:14:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 30-22:14:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 30-22:14:30 (3372) [INFO] : wp-toolkit-thirdparties * 30-22:14:30 (3372) [INFO] Cleaning up list of fastest mirrors * 30-22:14:30 (3382) [INFO]  * 30-22:14:30 (3361) [INFO] Running: /usr/bin/yum check-update * 30-22:14:30 (3362) [INFO]  * 30-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:31 (3372) [INFO] Determining fastest mirrors * 30-22:14:33 (3372) [INFO] * EA4: 185.15.22.168 * 30-22:14:33 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 30-22:14:33 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 30-22:14:33 (3372) [INFO] * epel: lon.mirror.rackspace.com * 30-22:14:51 (3372) [INFO]  * 30-22:14:51 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 30-22:14:51 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-22:14:51 (3382) [INFO]  * 30-22:14:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-22:14:51 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-22:14:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-22:14:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-22:14:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-30_22:14:52_modified_for_AlmaLinux_8.json * 30-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 30-22:14:52 (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-22:14:52 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 31-22:14:43 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 31-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 31-22:14: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  * 31-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 31-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 31-22:15:13 (3362) [INFO]  * 31-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:15:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 31-22:15:14 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-22:15:14 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 31-22:15:14 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 31-22:15:14 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 31-22:15:14 (3372) [INFO] : wp-toolkit-thirdparties * 31-22:15:14 (3372) [INFO] Cleaning up list of fastest mirrors * 31-22:15:14 (3382) [INFO]  * 31-22:15:14 (3361) [INFO] Running: /usr/bin/yum check-update * 31-22:15:14 (3362) [INFO]  * 31-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:15:14 (3372) [INFO] Determining fastest mirrors * 31-22:15:20 (3372) [INFO] * EA4: 185.15.22.168 * 31-22:15:20 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 31-22:15:20 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 31-22:15:20 (3372) [INFO] * epel: mirrors.20i.com * 31-22:15:37 (3372) [INFO]  * 31-22:15:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 31-22:15:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-22:15:37 (3382) [INFO]  * 31-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 31-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 31-22:15:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2022-12-31_22:15:38_modified_for_AlmaLinux_8.json * 31-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 31-22:15: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.  * 31-22:15:38 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:14:37 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:14:40 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:40 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:40 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:14: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  * 01-22:15:10 (2925) [INFO] Checking if your system is up to date:  * 01-22:15:10 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:15:10 (3362) [INFO]  * 01-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:15:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:15:10 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:15:10 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:15:10 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:15:10 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:15:10 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:15:10 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:15:10 (3382) [INFO]  * 01-22:15:10 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:15:10 (3362) [INFO]  * 01-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:15:10 (3372) [INFO] Determining fastest mirrors * 01-22:15:14 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:15:14 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:15:14 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:15:14 (3372) [INFO] * epel: lon.mirror.rackspace.com * 01-22:15:31 (3372) [INFO]  * 01-22:15:31 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 01-22:15:31 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:15:32 (3382) [INFO]  * 01-22:15:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:15:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:15:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:15:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:15:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-01_22:15:32_modified_for_AlmaLinux_8.json * 01-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:15: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.  * 01-22:15:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:13:59 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:02 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:14:02 (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-22:14:25 (2925) [INFO] Checking if your system is up to date:  * 02-22:14:25 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:14:25 (3362) [INFO]  * 02-22:14:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:14:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:14:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:14:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:14:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:14:25 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:14:26 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:14:26 (3382) [INFO]  * 02-22:14:26 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:14:26 (3362) [INFO]  * 02-22:14:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:26 (3372) [INFO] Determining fastest mirrors * 02-22:14:30 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:14:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:14:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:14:30 (3372) [INFO] * epel: lon.mirror.rackspace.com * 02-22:14:48 (3372) [INFO]  * 02-22:14:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 02-22:14:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:14:48 (3382) [INFO]  * 02-22:14:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:14:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:14:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:14:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:14:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-02_22:14:49_modified_for_AlmaLinux_8.json * 02-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:14: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.  * 02-22:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:08 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 03-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:14:32 (3362) [INFO]  * 03-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:14:33 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:14:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:14:33 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:14:33 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:14:33 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:14:33 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:14:33 (3382) [INFO]  * 03-22:14:33 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:14:33 (3362) [INFO]  * 03-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:33 (3372) [INFO] Determining fastest mirrors * 03-22:14:37 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:14:37 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:14:37 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:14:37 (3372) [INFO] * epel: mirrors.20i.com * 03-22:14:55 (3372) [INFO]  * 03-22:14:55 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 03-22:14:55 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:14:55 (3382) [INFO]  * 03-22:14:55 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:14:55 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:14:55 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:14:55 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:14:56 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-03_22:14:56_modified_for_AlmaLinux_8.json * 03-22:14:56 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:14:56 (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-22:14:56 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:22 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:24 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:24 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:24 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14:24 (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-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 04-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:14:57 (3362) [INFO]  * 04-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:14:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:14:57 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:14:57 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:14:57 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:14:57 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:14:57 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:14:57 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:14:58 (3382) [INFO]  * 04-22:14:58 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:14:58 (3362) [INFO]  * 04-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:14:58 (3372) [INFO] Determining fastest mirrors * 04-22:15:01 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:15:01 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:15:01 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:15:01 (3372) [INFO] * epel: lon.mirror.rackspace.com * 04-22:15:20 (3372) [INFO]  * 04-22:15:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 04-22:15:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:20 (3382) [INFO]  * 04-22:15:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-04_22:15:21_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15: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.  * 04-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:15:09 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:15:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:15:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:15:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:15: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  * 05-22:15:36 (2925) [INFO] Checking if your system is up to date:  * 05-22:15:36 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:15:36 (3362) [INFO]  * 05-22:15:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:15:36 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:15:36 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:15:36 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:15:36 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:15:36 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:15:36 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:15:36 (3382) [INFO]  * 05-22:15:36 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:15:36 (3362) [INFO]  * 05-22:15:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:37 (3372) [INFO] Determining fastest mirrors * 05-22:15:39 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:15:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:15:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:15:39 (3372) [INFO] * epel: lon.mirror.rackspace.com * 05-22:15:56 (3372) [INFO]  * 05-22:15:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 05-22:15:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:15:56 (3382) [INFO]  * 05-22:15:56 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:15:56 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:15:56 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:15:56 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:15:57 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-05_22:15:57_modified_for_AlmaLinux_8.json * 05-22:15:57 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:15:57 (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-22:15:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:14:01 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:14: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  * 06-22:14:26 (2925) [INFO] Checking if your system is up to date:  * 06-22:14:26 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:14:26 (3362) [INFO]  * 06-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:14:27 (3382) [INFO]  * 06-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:14:27 (3362) [INFO]  * 06-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:27 (3372) [INFO] Determining fastest mirrors * 06-22:14:30 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:14:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:14:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:14:30 (3372) [INFO] * epel: lon.mirror.rackspace.com * 06-22:14:48 (3372) [INFO]  * 06-22:14:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 06-22:14:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:14:48 (3382) [INFO]  * 06-22:14:48 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:14:48 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:14:48 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:14:48 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:14:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-06_22:14:49_modified_for_AlmaLinux_8.json * 06-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:14: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.  * 06-22:14:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:14:39 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:41 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:41 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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  * 07-22:15:08 (2925) [INFO] Checking if your system is up to date:  * 07-22:15:08 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:15:08 (3362) [INFO]  * 07-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:15:09 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:15:09 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:15:09 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:15:09 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:15:09 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:15:09 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:15:09 (3382) [INFO]  * 07-22:15:09 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:15:09 (3362) [INFO]  * 07-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:15:09 (3372) [INFO] Determining fastest mirrors * 07-22:15:13 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:15:13 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:15:13 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:15:13 (3372) [INFO] * epel: lon.mirror.rackspace.com * 07-22:15:32 (3372) [INFO]  * 07-22:15:32 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 07-22:15:32 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:15:32 (3382) [INFO]  * 07-22:15:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:15:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:15:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:15:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:15:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-07_22:15:32_modified_for_AlmaLinux_8.json * 07-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:15: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.  * 07-22:15:33 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:14:41 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:43 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:14: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  * 08-22:15:09 (2925) [INFO] Checking if your system is up to date:  * 08-22:15:09 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:15:09 (3362) [INFO]  * 08-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:15:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:15:09 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:15:09 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:15:09 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:15:09 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:15:09 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:15:09 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:15:09 (3382) [INFO]  * 08-22:15:09 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:15:09 (3362) [INFO]  * 08-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:15:10 (3372) [INFO] Determining fastest mirrors * 08-22:15:13 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:15:13 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:15:13 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:15:13 (3372) [INFO] * epel: mirrors.20i.com * 08-22:15:31 (3372) [INFO]  * 08-22:15:31 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 08-22:15:31 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:15:31 (3382) [INFO]  * 08-22:15:31 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:15:31 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:15:31 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:15:31 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:15:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-08_22:15:32_modified_for_AlmaLinux_8.json * 08-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:15: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.  * 08-22:15:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:13:56 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:13:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:13:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:13:57 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:13: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  * 09-22:14:20 (2925) [INFO] Checking if your system is up to date:  * 09-22:14:20 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:14:20 (3362) [INFO]  * 09-22:14:20 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:20 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:14:20 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:14:20 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:14:20 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:14:20 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:14:20 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:14:20 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:14:20 (3382) [INFO]  * 09-22:14:20 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:14:20 (3362) [INFO]  * 09-22:14:21 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:21 (3372) [INFO] Determining fastest mirrors * 09-22:14:23 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:14:23 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:14:23 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:14:23 (3372) [INFO] * epel: lon.mirror.rackspace.com * 09-22:14:42 (3372) [INFO]  * 09-22:14:42 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 09-22:14:42 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:14:42 (3382) [INFO]  * 09-22:14:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:14:42 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:14:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:14:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:14:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-09_22:14:43_modified_for_AlmaLinux_8.json * 09-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:14: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.  * 09-22:14:43 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:14:58 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:15:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:00 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:00 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:15: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  * 10-22:15:22 (2925) [INFO] Checking if your system is up to date:  * 10-22:15:22 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:15:22 (3362) [INFO]  * 10-22:15:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:15:23 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:15:23 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:15:23 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:15:23 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:15:23 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:15:23 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:15:23 (3382) [INFO]  * 10-22:15:23 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:15:23 (3362) [INFO]  * 10-22:15:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:15:23 (3372) [INFO] Determining fastest mirrors * 10-22:15:28 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:15:28 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:15:28 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:15:28 (3372) [INFO] * epel: lon.mirror.rackspace.com * 10-22:15:48 (3372) [INFO]  * 10-22:15:48 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 10-22:15:48 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:15:49 (3382) [INFO]  * 10-22:15:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:15:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:15:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:15:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:15:49 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-10_22:15:49_modified_for_AlmaLinux_8.json * 10-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:15: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.  * 10-22:15:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:13:56 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:13:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:13: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  * 11-22:14:24 (2925) [INFO] Checking if your system is up to date:  * 11-22:14:24 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:14:24 (3362) [INFO]  * 11-22:14:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:14:24 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:14:24 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:14:24 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:14:24 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:14:24 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:14:24 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:14:26 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:14:26 (3382) [INFO]  * 11-22:14:26 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:14:26 (3362) [INFO]  * 11-22:14:26 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:14:26 (3372) [INFO] Determining fastest mirrors * 11-22:14:28 (3372) [INFO] * EA4: 185.15.22.168 * 11-22:14:28 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 11-22:14:28 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 11-22:14:28 (3372) [INFO] * epel: lon.mirror.rackspace.com * 11-22:14:46 (3372) [INFO]  * 11-22:14:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 11-22:14:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-22:14:47 (3382) [INFO]  * 11-22:14:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:14:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:14:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:14:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-11_22:14:47_modified_for_AlmaLinux_8.json * 11-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:14: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.  * 11-22:14:48 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:14:31 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:14:32 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:32 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:14:32 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:14: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  * 12-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 12-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:14:57 (3362) [INFO]  * 12-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:14:57 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:14:57 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:14:57 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:14:57 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:14:57 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:14:57 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:14:57 (3382) [INFO]  * 12-22:14:57 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:14:57 (3362) [INFO]  * 12-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:14:58 (3372) [INFO] Determining fastest mirrors * 12-22:15:01 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:15:01 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:15:01 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:15:01 (3372) [INFO] * epel: mirrors.20i.com * 12-22:15:20 (3372) [INFO]  * 12-22:15:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 12-22:15:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:15:20 (3382) [INFO]  * 12-22:15:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:15:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:15:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:15:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-12_22:15:21_modified_for_AlmaLinux_8.json * 12-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:15: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.  * 12-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14: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  * 13-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 13-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:14:32 (3362) [INFO]  * 13-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:14:32 (3382) [INFO]  * 13-22:14:32 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:14:32 (3362) [INFO]  * 13-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:33 (3372) [INFO] Determining fastest mirrors * 13-22:14:34 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * epel: lon.mirror.rackspace.com * 13-22:14:51 (3372) [INFO]  * 13-22:14:51 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 13-22:14:51 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:14:52 (3382) [INFO]  * 13-22:14:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:14:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:14:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:14:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-13_22:14:52_modified_for_AlmaLinux_8.json * 13-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:14: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.  * 13-22:14:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:14:48 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:14:53 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:53 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:53 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:14: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  * 14-22:15:18 (2925) [INFO] Checking if your system is up to date:  * 14-22:15:18 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:15:18 (3362) [INFO]  * 14-22:15:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:15:18 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:15:18 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:15:18 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:15:18 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:15:18 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:15:18 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:15:18 (3382) [INFO]  * 14-22:15:18 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:15:18 (3362) [INFO]  * 14-22:15:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:15:19 (3372) [INFO] Determining fastest mirrors * 14-22:15:22 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:15:22 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:15:22 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:15:22 (3372) [INFO] * epel: mirrors.20i.com * 14-22:15:42 (3372) [INFO]  * 14-22:15:42 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 14-22:15:42 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:15:42 (3382) [INFO]  * 14-22:15:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:15:42 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:15:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:15:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:15:43 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-14_22:15:43_modified_for_AlmaLinux_8.json * 14-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:15: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.  * 14-22:15:43 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:14:40 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:14:42 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:42 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:42 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:14: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  * 15-22:15:10 (2925) [INFO] Checking if your system is up to date:  * 15-22:15:10 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:15:10 (3362) [INFO]  * 15-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:15:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:15:10 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:15:10 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:15:10 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:15:10 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:15:10 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:15:10 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:15:10 (3382) [INFO]  * 15-22:15:10 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:15:10 (3362) [INFO]  * 15-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:15:10 (3372) [INFO] Determining fastest mirrors * 15-22:15:24 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:15:24 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:15:24 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:15:24 (3372) [INFO] * epel: lon.mirror.rackspace.com * 15-22:15:41 (3372) [INFO]  * 15-22:15:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 15-22:15:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:15:41 (3382) [INFO]  * 15-22:15:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:15:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:15:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:15:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:15:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-15_22:15:42_modified_for_AlmaLinux_8.json * 15-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:15: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.  * 15-22:15:42 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:14:04 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:14: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  * 16-22:14:35 (2925) [INFO] Checking if your system is up to date:  * 16-22:14:35 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:14:35 (3362) [INFO]  * 16-22:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:14:35 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:14:35 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:14:35 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:14:35 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:14:35 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:14:35 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:14:35 (3382) [INFO]  * 16-22:14:35 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:14:35 (3362) [INFO]  * 16-22:14:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:36 (3372) [INFO] Determining fastest mirrors * 16-22:14:39 (3372) [INFO] * EA4: 185.15.22.168 * 16-22:14:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 16-22:14:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 16-22:14:39 (3372) [INFO] * epel: mirrors.20i.com * 16-22:14:57 (3372) [INFO]  * 16-22:14:57 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 16-22:14:57 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:14:57 (3382) [INFO]  * 16-22:14:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:14:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:14:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:14:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-16_22:14:58_modified_for_AlmaLinux_8.json * 16-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:14: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-22:14:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:15:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:15:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:15:45 (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-22:16:11 (2925) [INFO] Checking if your system is up to date:  * 17-22:16:11 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:16:11 (3362) [INFO]  * 17-22:16:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:16:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:16:11 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:16:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:16:11 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:16:11 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:16:11 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:16:11 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:16:11 (3382) [INFO]  * 17-22:16:11 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:16:11 (3362) [INFO]  * 17-22:16:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:16:12 (3372) [INFO] Determining fastest mirrors * 17-22:16:15 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:16:15 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:16:15 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:16:15 (3372) [INFO] * epel: lon.mirror.rackspace.com * 17-22:16:34 (3372) [INFO]  * 17-22:16:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 17-22:16:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:16:34 (3382) [INFO]  * 17-22:16:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:16:34 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:16:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:16:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:16:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-17_22:16:35_modified_for_AlmaLinux_8.json * 17-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:16: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.  * 17-22:16:35 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:14: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  * 18-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 18-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:14:32 (3362) [INFO]  * 18-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:14:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:14:33 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:14:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:14:33 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:14:33 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:14:33 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:14:33 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:14:33 (3382) [INFO]  * 18-22:14:33 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:14:33 (3362) [INFO]  * 18-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:14:33 (3372) [INFO] Determining fastest mirrors * 18-22:14:37 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:14:37 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:14:37 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:14:37 (3372) [INFO] * epel: mirrors.20i.com * 18-22:14:56 (3372) [INFO]  * 18-22:14:56 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 18-22:14:56 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:14:57 (3382) [INFO]  * 18-22:14:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:14:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:14:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:14:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:14:57 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-18_22:14:57_modified_for_AlmaLinux_8.json * 18-22:14:57 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:14:57 (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-22:14:57 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:15:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:15:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:15: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  * 19-22:15:30 (2925) [INFO] Checking if your system is up to date:  * 19-22:15:30 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:15:30 (3362) [INFO]  * 19-22:15:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:15:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:15:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:15:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:15:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:15:30 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:15:30 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:15:30 (3382) [INFO]  * 19-22:15:30 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:15:30 (3362) [INFO]  * 19-22:15:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:31 (3372) [INFO] Determining fastest mirrors * 19-22:15:34 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:15:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:15:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:15:34 (3372) [INFO] * epel: mirrors.20i.com * 19-22:15:52 (3372) [INFO]  * 19-22:15:52 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 19-22:15:52 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:15:52 (3382) [INFO]  * 19-22:15:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:15:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:15:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:15:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:15:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-19_22:15:53_modified_for_AlmaLinux_8.json * 19-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:15: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.  * 19-22:15:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:15:08 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:15:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:15:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:15:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:15: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  * 20-22:15:34 (2925) [INFO] Checking if your system is up to date:  * 20-22:15:34 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:15:34 (3362) [INFO]  * 20-22:15:34 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:15:34 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:15:34 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:15:34 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:15:34 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:15:34 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:15:34 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:15:35 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:15:35 (3382) [INFO]  * 20-22:15:35 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:15:35 (3362) [INFO]  * 20-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:15:35 (3372) [INFO] Determining fastest mirrors * 20-22:15:39 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:15:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:15:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:15:39 (3372) [INFO] * epel: mirrors.20i.com * 20-22:15:58 (3372) [INFO]  * 20-22:15:58 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 20-22:15:58 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:15:58 (3382) [INFO]  * 20-22:15:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:15:58 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:15:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:15:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:15:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-20_22:15:59_modified_for_AlmaLinux_8.json * 20-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:15: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.  * 20-22:15:59 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:14:47 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:49 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:49 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:14: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  * 21-22:15:19 (2925) [INFO] Checking if your system is up to date:  * 21-22:15:19 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:15:19 (3362) [INFO]  * 21-22:15:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:15:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:15:19 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:15:19 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:15:19 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:15:19 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:15:19 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:15:19 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:15:19 (3382) [INFO]  * 21-22:15:19 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:15:19 (3362) [INFO]  * 21-22:15:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:15:20 (3372) [INFO] Determining fastest mirrors * 21-22:15:23 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:15:23 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:15:23 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:15:23 (3372) [INFO] * epel: mirrors.20i.com * 21-22:15:41 (3372) [INFO]  * 21-22:15:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 21-22:15:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:15:41 (3382) [INFO]  * 21-22:15:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:15:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:15:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:15:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:15:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-21_22:15:42_modified_for_AlmaLinux_8.json * 21-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:15: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.  * 21-22:15:42 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:14:43 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:14:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:14:45 (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-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 22-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:15:12 (3362) [INFO]  * 22-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:15:13 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:15:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:15:13 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:15:13 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:15:13 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:15:13 (3382) [INFO]  * 22-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:15:13 (3362) [INFO]  * 22-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:13 (3372) [INFO] Determining fastest mirrors * 22-22:15:17 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:15:17 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:15:17 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:15:17 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 22-22:15:34 (3372) [INFO]  * 22-22:15:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 22-22:15:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:15:34 (3382) [INFO]  * 22-22:15:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:15:34 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:15:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:15:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:15:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-22_22:15:35_modified_for_AlmaLinux_8.json * 22-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:15: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.  * 22-22:15:35 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:13:57 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:13:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:13: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  * 23-22:14:25 (2925) [INFO] Checking if your system is up to date:  * 23-22:14:25 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:14:25 (3362) [INFO]  * 23-22:14:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:14:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:14:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:14:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:14:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:14:25 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:14:25 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:14:25 (3382) [INFO]  * 23-22:14:25 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:14:25 (3362) [INFO]  * 23-22:14:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:14:26 (3372) [INFO] Determining fastest mirrors * 23-22:14:29 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:14:29 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:14:29 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:14:29 (3372) [INFO] * epel: mirrors.ukfast.co.uk * 23-22:14:46 (3372) [INFO]  * 23-22:14:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 23-22:14:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:14:46 (3382) [INFO]  * 23-22:14:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:14:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:14:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:14:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:14:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-23_22:14:47_modified_for_AlmaLinux_8.json * 23-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:14: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.  * 23-22:14:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:14:06 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:14: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  * 24-22:14:31 (2925) [INFO] Checking if your system is up to date:  * 24-22:14:31 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:14:31 (3362) [INFO]  * 24-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:14:32 (3382) [INFO]  * 24-22:14:32 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:14:32 (3362) [INFO]  * 24-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:33 (3372) [INFO] Determining fastest mirrors * 24-22:14:36 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:14:36 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:14:36 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:14:36 (3372) [INFO] * epel: lon.mirror.rackspace.com * 24-22:14:54 (3372) [INFO]  * 24-22:14:54 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 24-22:14:54 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:14:54 (3382) [INFO]  * 24-22:14:54 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:14:54 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:14:54 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:14:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-24_22:14:55_modified_for_AlmaLinux_8.json * 24-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:14: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.  * 24-22:14:55 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:14:55 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:55 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:14:55 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:14: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  * 25-22:15:21 (2925) [INFO] Checking if your system is up to date:  * 25-22:15:21 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:15:21 (3362) [INFO]  * 25-22:15:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:23 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:15:23 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:15:23 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:15:23 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:15:23 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:15:23 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:15:23 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:15:23 (3382) [INFO]  * 25-22:15:23 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:15:23 (3362) [INFO]  * 25-22:15:23 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:23 (3372) [INFO] Determining fastest mirrors * 25-22:15:32 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:15:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:15:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:15:32 (3372) [INFO] * epel: mirrors.20i.com * 25-22:15:49 (3372) [INFO]  * 25-22:15:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 25-22:15:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:15:49 (3382) [INFO]  * 25-22:15:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:15:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:15:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:15:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:15:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-25_22:15:50_modified_for_AlmaLinux_8.json * 25-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:15: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.  * 25-22:15:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:13:56 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:13:59 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:13:59 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:13: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  * 26-22:14:22 (2925) [INFO] Checking if your system is up to date:  * 26-22:14:22 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:14:22 (3362) [INFO]  * 26-22:14:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:22 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:14:22 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:14:22 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:14:22 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:14:22 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:14:22 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:14:22 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:14:22 (3382) [INFO]  * 26-22:14:22 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:14:22 (3362) [INFO]  * 26-22:14:22 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:14:23 (3372) [INFO] Determining fastest mirrors * 26-22:14:24 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:14:24 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:14:24 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:14:24 (3372) [INFO] * epel: lon.mirror.rackspace.com * 26-22:14:45 (3372) [INFO]  * 26-22:14:45 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 26-22:14:45 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:14:45 (3382) [INFO]  * 26-22:14:45 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:14:45 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:14:45 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:14:45 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:14:46 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-26_22:14:46_modified_for_AlmaLinux_8.json * 26-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:14: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.  * 26-22:14:46 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:04 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:06 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14: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-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 27-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:14:32 (3362) [INFO]  * 27-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:14:33 (3382) [INFO]  * 27-22:14:33 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:14:33 (3362) [INFO]  * 27-22:14:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:33 (3372) [INFO] Determining fastest mirrors * 27-22:14:35 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:14:35 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:14:35 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:14:35 (3372) [INFO] * epel: lon.mirror.rackspace.com * 27-22:14:53 (3372) [INFO]  * 27-22:14:53 (3372) [INFO] kernel.x86_64 3.10.0-1160.81.1.el7 updates * 27-22:14:53 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:14:53 (3382) [INFO]  * 27-22:14:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:14:53 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:14:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:14:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:14:54 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-27_22:14:54_modified_for_AlmaLinux_8.json * 27-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:14: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.  * 27-22:14:54 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:15:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:15:03 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:15:03 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:15: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  * 28-22:15:24 (2925) [INFO] Checking if your system is up to date:  * 28-22:15:24 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:15:24 (3362) [INFO]  * 28-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:15:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:15:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:15:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:15:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:15:25 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:15:25 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:15:25 (3382) [INFO]  * 28-22:15:25 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:15:25 (3362) [INFO]  * 28-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:25 (3372) [INFO] Determining fastest mirrors * 28-22:15:29 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:15:29 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:15:29 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:15:29 (3372) [INFO] * epel: mirrors.20i.com * 28-22:15:46 (3372) [INFO]  * 28-22:15:46 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 28-22:15:46 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:15:46 (3382) [INFO]  * 28-22:15:46 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:15:46 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:15:46 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:15:46 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:15:47 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-28_22:15:47_modified_for_AlmaLinux_8.json * 28-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:15: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.  * 28-22:15:47 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 29-22:14:37 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 29-22:14:39 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:14:39 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 29-22:14:39 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 29-22:14: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  * 29-22:15:10 (2925) [INFO] Checking if your system is up to date:  * 29-22:15:10 (3361) [INFO] Running: /usr/bin/yum clean all * 29-22:15:10 (3362) [INFO]  * 29-22:15:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:11 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 29-22:15:11 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 29-22:15:11 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 29-22:15:11 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 29-22:15:11 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 29-22:15:11 (3372) [INFO] : wp-toolkit-thirdparties * 29-22:15:11 (3372) [INFO] Cleaning up list of fastest mirrors * 29-22:15:11 (3382) [INFO]  * 29-22:15:11 (3361) [INFO] Running: /usr/bin/yum check-update * 29-22:15:11 (3362) [INFO]  * 29-22:15:11 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 29-22:15:11 (3372) [INFO] Determining fastest mirrors * 29-22:15:16 (3372) [INFO] * EA4: 185.15.22.168 * 29-22:15:16 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 29-22:15:16 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 29-22:15:16 (3372) [INFO] * epel: lon.mirror.rackspace.com * 29-22:15:34 (3372) [INFO]  * 29-22:15:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 29-22:15:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 29-22:15:35 (3382) [INFO]  * 29-22:15:35 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 29-22:15:35 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 29-22:15:35 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 29-22:15:35 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 29-22:15:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-29_22:15:35_modified_for_AlmaLinux_8.json * 29-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 29-22:15: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.  * 29-22:15:35 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 30-22:14:06 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 30-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 30-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 30-22:14: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  * 30-22:14:30 (2925) [INFO] Checking if your system is up to date:  * 30-22:14:30 (3361) [INFO] Running: /usr/bin/yum clean all * 30-22:14:30 (3362) [INFO]  * 30-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:31 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 30-22:14:31 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 30-22:14:31 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 30-22:14:31 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 30-22:14:31 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 30-22:14:31 (3372) [INFO] : wp-toolkit-thirdparties * 30-22:14:31 (3372) [INFO] Cleaning up list of fastest mirrors * 30-22:14:31 (3382) [INFO]  * 30-22:14:31 (3361) [INFO] Running: /usr/bin/yum check-update * 30-22:14:31 (3362) [INFO]  * 30-22:14:31 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 30-22:14:31 (3372) [INFO] Determining fastest mirrors * 30-22:14:34 (3372) [INFO] * EA4: 185.15.22.168 * 30-22:14:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 30-22:14:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 30-22:14:34 (3372) [INFO] * epel: lon.mirror.rackspace.com * 30-22:14:52 (3372) [INFO]  * 30-22:14:52 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 30-22:14:52 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 30-22:14:52 (3382) [INFO]  * 30-22:14:52 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 30-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 30-22:14:52 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 30-22:14:52 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 30-22:14:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-30_22:14:53_modified_for_AlmaLinux_8.json * 30-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 30-22:14: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.  * 30-22:14:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 31-22:14:10 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 31-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:14:14 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 31-22:14:14 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 31-22:14: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  * 31-22:14:40 (2925) [INFO] Checking if your system is up to date:  * 31-22:14:40 (3361) [INFO] Running: /usr/bin/yum clean all * 31-22:14:40 (3362) [INFO]  * 31-22:14:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:14:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 31-22:14:41 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 31-22:14:41 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 31-22:14:41 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 31-22:14:41 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 31-22:14:41 (3372) [INFO] : wp-toolkit-thirdparties * 31-22:14:41 (3372) [INFO] Cleaning up list of fastest mirrors * 31-22:14:41 (3382) [INFO]  * 31-22:14:41 (3361) [INFO] Running: /usr/bin/yum check-update * 31-22:14:41 (3362) [INFO]  * 31-22:14:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 31-22:14:42 (3372) [INFO] Determining fastest mirrors * 31-22:14:45 (3372) [INFO] * EA4: 185.15.22.168 * 31-22:14:45 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 31-22:14:45 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 31-22:14:45 (3372) [INFO] * epel: mirrors.20i.com * 31-22:15:04 (3372) [INFO]  * 31-22:15:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 31-22:15:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 31-22:15:04 (3382) [INFO]  * 31-22:15:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 31-22:15:04 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 31-22:15:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 31-22:15:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 31-22:15:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-01-31_22:15:05_modified_for_AlmaLinux_8.json * 31-22:15:05 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 31-22:15: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.  * 31-22:15:05 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:14:14 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:14:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:16 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:14: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  * 01-22:14:37 (2925) [INFO] Checking if your system is up to date:  * 01-22:14:37 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:14:37 (3362) [INFO]  * 01-22:14:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:37 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:14:37 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:14:37 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:14:37 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:14:37 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:14:37 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:14:37 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:14:37 (3382) [INFO]  * 01-22:14:37 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:14:37 (3362) [INFO]  * 01-22:14:37 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:38 (3372) [INFO] Determining fastest mirrors * 01-22:14:39 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:14:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:14:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:14:39 (3372) [INFO] * epel: lon.mirror.rackspace.com * 01-22:14:58 (3372) [INFO]  * 01-22:14:58 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 01-22:14:58 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:14:58 (3382) [INFO]  * 01-22:14:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:14:58 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:14:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:14:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:14:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-01_22:14:59_modified_for_AlmaLinux_8.json * 01-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:14: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-22:14:59 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:14:53 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:14:54 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:54 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:54 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:14: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  * 02-22:15:19 (2925) [INFO] Checking if your system is up to date:  * 02-22:15:19 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:15:19 (3362) [INFO]  * 02-22:15:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:15:19 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:15:19 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:15:19 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:15:19 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:15:19 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:15:19 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:15:19 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:15:19 (3382) [INFO]  * 02-22:15:19 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:15:19 (3362) [INFO]  * 02-22:15:19 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:15:20 (3372) [INFO] Determining fastest mirrors * 02-22:15:22 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:15:22 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:15:22 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:15:22 (3372) [INFO] * epel: mirrors.20i.com * 02-22:15:41 (3372) [INFO]  * 02-22:15:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 02-22:15:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:15:42 (3382) [INFO]  * 02-22:15:42 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:15:42 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:15:42 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:15:42 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:15:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-02_22:15:42_modified_for_AlmaLinux_8.json * 02-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:15: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.  * 02-22:15:43 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:17 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:18 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:18 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:14:42 (2925) [INFO] Checking if your system is up to date:  * 03-22:14:42 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:14:42 (3362) [INFO]  * 03-22:14:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:42 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:14:42 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:14:42 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:14:42 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:14:42 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:14:42 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:14:42 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:14:42 (3382) [INFO]  * 03-22:14:42 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:14:42 (3362) [INFO]  * 03-22:14:43 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:43 (3372) [INFO] Determining fastest mirrors * 03-22:14:46 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:14:46 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:14:46 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:14:46 (3372) [INFO] * epel: mirrors.20i.com * 03-22:15:05 (3372) [INFO]  * 03-22:15:05 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 03-22:15:05 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:15:05 (3382) [INFO]  * 03-22:15:05 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:15:05 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:15:05 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:15:05 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:15:06 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-03_22:15:06_modified_for_AlmaLinux_8.json * 03-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:15: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.  * 03-22:15:06 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:43 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:45 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:45 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14:45 (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-22:15:13 (2925) [INFO] Checking if your system is up to date:  * 04-22:15:13 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:15:13 (3362) [INFO]  * 04-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:14 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:15:14 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:15:14 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:15:14 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:15:14 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:15:14 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:15:14 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:15:14 (3382) [INFO]  * 04-22:15:14 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:15:14 (3362) [INFO]  * 04-22:15:14 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:14 (3372) [INFO] Determining fastest mirrors * 04-22:15:18 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:15:18 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:15:18 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:15:18 (3372) [INFO] * epel: mirrors.20i.com * 04-22:15:36 (3372) [INFO]  * 04-22:15:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 04-22:15:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:37 (3382) [INFO]  * 04-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-04_22:15:37_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15: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.  * 04-22:15:37 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:14: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  * 05-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 05-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:15:12 (3362) [INFO]  * 05-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:13 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:15:13 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:15:13 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:15:13 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:15:13 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:15:13 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:15:13 (3382) [INFO]  * 05-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:15:13 (3362) [INFO]  * 05-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:13 (3372) [INFO] Determining fastest mirrors * 05-22:15:16 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:15:16 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:15:16 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:15:16 (3372) [INFO] * epel: mirrors.20i.com * 05-22:15:34 (3372) [INFO]  * 05-22:15:34 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 05-22:15:34 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:15:34 (3382) [INFO]  * 05-22:15:34 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:15:34 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:15:34 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:15:34 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:15:35 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-05_22:15:35_modified_for_AlmaLinux_8.json * 05-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:15: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.  * 05-22:15:35 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:14:03 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:05 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:14:05 (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-22:14:29 (2925) [INFO] Checking if your system is up to date:  * 06-22:14:29 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:14:29 (3362) [INFO]  * 06-22:14:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:29 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:14:29 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:14:29 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:14:29 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:14:29 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:14:29 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:14:29 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:14:30 (3382) [INFO]  * 06-22:14:30 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:14:30 (3362) [INFO]  * 06-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:30 (3372) [INFO] Determining fastest mirrors * 06-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * epel: mirrors.20i.com * 06-22:14:49 (3372) [INFO]  * 06-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 06-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:14:49 (3382) [INFO]  * 06-22:14:49 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:14:49 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:14:49 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:14:49 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-06_22:14:50_modified_for_AlmaLinux_8.json * 06-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:14: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.  * 06-22:14:50 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:13:59 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:01 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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  * 07-22:14:27 (2925) [INFO] Checking if your system is up to date:  * 07-22:14:27 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:14:27 (3362) [INFO]  * 07-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:14:28 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:14:28 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:14:28 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:14:28 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:14:28 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:14:29 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:14:29 (3382) [INFO]  * 07-22:14:29 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:14:29 (3362) [INFO]  * 07-22:14:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:29 (3372) [INFO] Determining fastest mirrors * 07-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:14:32 (3372) [INFO] * epel: mirrors.20i.com * 07-22:14:50 (3372) [INFO]  * 07-22:14:50 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 07-22:14:50 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:14:50 (3382) [INFO]  * 07-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:14:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:14:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:14:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-07_22:14:51_modified_for_AlmaLinux_8.json * 07-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:14: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-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:14:02 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:05 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:14:05 (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-22:14:28 (2925) [INFO] Checking if your system is up to date:  * 08-22:14:28 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:14:28 (3362) [INFO]  * 08-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:29 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:14:29 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:14:29 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:14:29 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:14:29 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:14:29 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:14:29 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:14:29 (3382) [INFO]  * 08-22:14:29 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:14:29 (3362) [INFO]  * 08-22:14:29 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:29 (3372) [INFO] Determining fastest mirrors * 08-22:14:33 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:14:33 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:14:33 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:14:33 (3372) [INFO] * epel: mirrors.20i.com * 08-22:14:51 (3372) [INFO]  * 08-22:14:51 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 08-22:14:51 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:14:51 (3382) [INFO]  * 08-22:14:51 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:14:51 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:14:51 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:14:51 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:14:52 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-08_22:14:52_modified_for_AlmaLinux_8.json * 08-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:14:52 (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-22:14:52 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 09-22:14:32 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 09-22:14:35 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:35 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 09-22:14:35 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 09-22:14: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  * 09-22:14:58 (2925) [INFO] Checking if your system is up to date:  * 09-22:14:58 (3361) [INFO] Running: /usr/bin/yum clean all * 09-22:14:58 (3362) [INFO]  * 09-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:58 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 09-22:14:58 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 09-22:14:58 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 09-22:14:58 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 09-22:14:58 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 09-22:14:58 (3372) [INFO] : wp-toolkit-thirdparties * 09-22:14:58 (3372) [INFO] Cleaning up list of fastest mirrors * 09-22:14:58 (3382) [INFO]  * 09-22:14:58 (3361) [INFO] Running: /usr/bin/yum check-update * 09-22:14:58 (3362) [INFO]  * 09-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 09-22:14:59 (3372) [INFO] Determining fastest mirrors * 09-22:15:02 (3372) [INFO] * EA4: 185.15.22.168 * 09-22:15:02 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 09-22:15:02 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 09-22:15:02 (3372) [INFO] * epel: mirrors.20i.com * 09-22:15:20 (3372) [INFO]  * 09-22:15:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 09-22:15:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 09-22:15:20 (3382) [INFO]  * 09-22:15:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 09-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 09-22:15:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 09-22:15:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 09-22:15:20 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-09_22:15:20_modified_for_AlmaLinux_8.json * 09-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 09-22:15: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.  * 09-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 10-22:15:41 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 10-22:15:42 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:42 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 10-22:15:42 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 10-22:15: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  * 10-22:16:06 (2925) [INFO] Checking if your system is up to date:  * 10-22:16:06 (3361) [INFO] Running: /usr/bin/yum clean all * 10-22:16:06 (3362) [INFO]  * 10-22:16:06 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:16:07 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 10-22:16:07 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 10-22:16:07 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 10-22:16:07 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 10-22:16:07 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 10-22:16:07 (3372) [INFO] : wp-toolkit-thirdparties * 10-22:16:07 (3372) [INFO] Cleaning up list of fastest mirrors * 10-22:16:07 (3382) [INFO]  * 10-22:16:07 (3361) [INFO] Running: /usr/bin/yum check-update * 10-22:16:07 (3362) [INFO]  * 10-22:16:07 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 10-22:16:07 (3372) [INFO] Determining fastest mirrors * 10-22:16:12 (3372) [INFO] * EA4: 185.15.22.168 * 10-22:16:12 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 10-22:16:12 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 10-22:16:12 (3372) [INFO] * epel: mirrors.20i.com * 10-22:16:33 (3372) [INFO]  * 10-22:16:33 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 10-22:16:33 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 10-22:16:33 (3382) [INFO]  * 10-22:16:33 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 10-22:16:33 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 10-22:16:33 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 10-22:16:33 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 10-22:16:34 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-10_22:16:34_modified_for_AlmaLinux_8.json * 10-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 10-22:16: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.  * 10-22:16:34 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 11-22:14:41 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 11-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:43 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 11-22:14:43 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 11-22:14: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-22:15:09 (2925) [INFO] Checking if your system is up to date:  * 11-22:15:09 (3361) [INFO] Running: /usr/bin/yum clean all * 11-22:15:09 (3362) [INFO]  * 11-22:15:09 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:09 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 11-22:15:09 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 11-22:15:09 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 11-22:15:09 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 11-22:15:09 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 11-22:15:09 (3372) [INFO] : wp-toolkit-thirdparties * 11-22:15:10 (3372) [INFO] Cleaning up list of fastest mirrors * 11-22:15:10 (3382) [INFO]  * 11-22:15:10 (3361) [INFO] Running: /usr/bin/yum check-update * 11-22:15:10 (3362) [INFO]  * 11-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 11-22:15:10 (3372) [INFO] Determining fastest mirrors * 11-22:15:14 (3372) [INFO] * EA4: 185.15.22.168 * 11-22:15:14 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 11-22:15:14 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 11-22:15:14 (3372) [INFO] * epel: mirrors.20i.com * 11-22:15:31 (3372) [INFO]  * 11-22:15:31 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 11-22:15:31 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 11-22:15:32 (3382) [INFO]  * 11-22:15:32 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 11-22:15:32 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 11-22:15:32 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 11-22:15:32 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 11-22:15:32 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-11_22:15:32_modified_for_AlmaLinux_8.json * 11-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 11-22:15: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.  * 11-22:15:32 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 12-22:15:04 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 12-22:15:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:15:05 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 12-22:15:05 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 12-22:15:05 (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-22:15:35 (2925) [INFO] Checking if your system is up to date:  * 12-22:15:35 (3361) [INFO] Running: /usr/bin/yum clean all * 12-22:15:35 (3362) [INFO]  * 12-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 12-22:15:35 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 12-22:15:35 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 12-22:15:35 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 12-22:15:35 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 12-22:15:35 (3372) [INFO] : wp-toolkit-thirdparties * 12-22:15:35 (3372) [INFO] Cleaning up list of fastest mirrors * 12-22:15:35 (3382) [INFO]  * 12-22:15:35 (3361) [INFO] Running: /usr/bin/yum check-update * 12-22:15:35 (3362) [INFO]  * 12-22:15:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 12-22:15:36 (3372) [INFO] Determining fastest mirrors * 12-22:15:40 (3372) [INFO] * EA4: 185.15.22.168 * 12-22:15:40 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 12-22:15:40 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 12-22:15:40 (3372) [INFO] * epel: mirrors.20i.com * 12-22:15:59 (3372) [INFO]  * 12-22:15:59 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 12-22:15:59 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 12-22:15:59 (3382) [INFO]  * 12-22:15:59 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 12-22:15:59 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 12-22:15:59 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 12-22:15:59 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 12-22:16:00 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-12_22:16:00_modified_for_AlmaLinux_8.json * 12-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 12-22:16: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.  * 12-22:16:00 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 13-22:14:07 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 13-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:09 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 13-22:14:09 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 13-22:14: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  * 13-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 13-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 13-22:14:32 (3362) [INFO]  * 13-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 13-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 13-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 13-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 13-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 13-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 13-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 13-22:14:32 (3382) [INFO]  * 13-22:14:32 (3361) [INFO] Running: /usr/bin/yum check-update * 13-22:14:32 (3362) [INFO]  * 13-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 13-22:14:33 (3372) [INFO] Determining fastest mirrors * 13-22:14:34 (3372) [INFO] * EA4: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 13-22:14:34 (3372) [INFO] * epel: mirrors.20i.com * 13-22:14:52 (3372) [INFO]  * 13-22:14:52 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 13-22:14:52 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 13-22:14:53 (3382) [INFO]  * 13-22:14:53 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 13-22:14:53 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 13-22:14:53 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 13-22:14:53 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 13-22:14:53 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-13_22:14:53_modified_for_AlmaLinux_8.json * 13-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 13-22:14: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.  * 13-22:14:53 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 14-22:14:45 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 14-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:48 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 14-22:14:48 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 14-22:14: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  * 14-22:14:57 (2925) [INFO] Checking if your system is up to date:  * 14-22:14:57 (3361) [INFO] Running: /usr/bin/yum clean all * 14-22:14:57 (3362) [INFO]  * 14-22:14:57 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:14:57 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 14-22:14:57 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 14-22:14:57 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 14-22:14:57 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 14-22:14:57 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 14-22:14:57 (3372) [INFO] : wp-toolkit-thirdparties * 14-22:14:57 (3372) [INFO] Cleaning up list of fastest mirrors * 14-22:14:57 (3382) [INFO]  * 14-22:14:57 (3361) [INFO] Running: /usr/bin/yum check-update * 14-22:14:57 (3362) [INFO]  * 14-22:14:58 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 14-22:14:58 (3372) [INFO] Determining fastest mirrors * 14-22:15:00 (3372) [INFO] * EA4: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 14-22:15:00 (3372) [INFO] * epel: lon.mirror.rackspace.com * 14-22:15:19 (3372) [INFO]  * 14-22:15:19 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 14-22:15:19 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 14-22:15:19 (3382) [INFO]  * 14-22:15:19 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 14-22:15:19 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 14-22:15:19 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 14-22:15:19 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 14-22:15:20 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-14_22:15:20_modified_for_AlmaLinux_8.json * 14-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 14-22:15: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.  * 14-22:15:20 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 15-22:14:23 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 15-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:26 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 15-22:14:26 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 15-22:14: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  * 15-22:14:51 (2925) [INFO] Checking if your system is up to date:  * 15-22:14:51 (3361) [INFO] Running: /usr/bin/yum clean all * 15-22:14:51 (3362) [INFO]  * 15-22:14:51 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:51 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 15-22:14:51 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 15-22:14:51 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 15-22:14:51 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 15-22:14:51 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 15-22:14:51 (3372) [INFO] : wp-toolkit-thirdparties * 15-22:14:52 (3372) [INFO] Cleaning up list of fastest mirrors * 15-22:14:52 (3382) [INFO]  * 15-22:14:52 (3361) [INFO] Running: /usr/bin/yum check-update * 15-22:14:52 (3362) [INFO]  * 15-22:14:52 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 15-22:14:52 (3372) [INFO] Determining fastest mirrors * 15-22:14:56 (3372) [INFO] * EA4: 185.15.22.168 * 15-22:14:56 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 15-22:14:56 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 15-22:14:56 (3372) [INFO] * epel: lon.mirror.rackspace.com * 15-22:15:15 (3372) [INFO]  * 15-22:15:15 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 15-22:15:15 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 15-22:15:15 (3382) [INFO]  * 15-22:15:15 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 15-22:15:15 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 15-22:15:15 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 15-22:15:15 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 15-22:15:16 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-15_22:15:16_modified_for_AlmaLinux_8.json * 15-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 15-22:15: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.  * 15-22:15:16 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 16-22:14:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 16-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:02 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 16-22:14:02 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 16-22:14:02 (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-22:14:27 (2925) [INFO] Checking if your system is up to date:  * 16-22:14:27 (3361) [INFO] Running: /usr/bin/yum clean all * 16-22:14:27 (3362) [INFO]  * 16-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 16-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 16-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 16-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 16-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 16-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 16-22:14:27 (3372) [INFO] Cleaning up list of fastest mirrors * 16-22:14:27 (3382) [INFO]  * 16-22:14:27 (3361) [INFO] Running: /usr/bin/yum check-update * 16-22:14:27 (3362) [INFO]  * 16-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 16-22:14:28 (3372) [INFO] Determining fastest mirrors * 16-22:14:30 (3372) [INFO] * EA4: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 16-22:14:30 (3372) [INFO] * epel: lon.mirror.rackspace.com * 16-22:14:49 (3372) [INFO]  * 16-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 16-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 16-22:14:50 (3382) [INFO]  * 16-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 16-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 16-22:14:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 16-22:14:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 16-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-16_22:14:50_modified_for_AlmaLinux_8.json * 16-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 16-22:14: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.  * 16-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 17-22:15:21 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 17-22:15:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:22 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 17-22:15:22 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 17-22:15: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-22:15:47 (2925) [INFO] Checking if your system is up to date:  * 17-22:15:47 (3361) [INFO] Running: /usr/bin/yum clean all * 17-22:15:47 (3362) [INFO]  * 17-22:15:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:48 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 17-22:15:48 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 17-22:15:48 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 17-22:15:48 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 17-22:15:48 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 17-22:15:48 (3372) [INFO] : wp-toolkit-thirdparties * 17-22:15:48 (3372) [INFO] Cleaning up list of fastest mirrors * 17-22:15:48 (3382) [INFO]  * 17-22:15:48 (3361) [INFO] Running: /usr/bin/yum check-update * 17-22:15:48 (3362) [INFO]  * 17-22:15:48 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 17-22:15:48 (3372) [INFO] Determining fastest mirrors * 17-22:15:51 (3372) [INFO] * EA4: 185.15.22.168 * 17-22:15:51 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 17-22:15:51 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 17-22:15:51 (3372) [INFO] * epel: lon.mirror.rackspace.com * 17-22:16:11 (3372) [INFO]  * 17-22:16:11 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 17-22:16:11 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 17-22:16:11 (3382) [INFO]  * 17-22:16:11 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 17-22:16:11 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 17-22:16:11 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 17-22:16:11 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 17-22:16:12 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-17_22:16:12_modified_for_AlmaLinux_8.json * 17-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 17-22:16: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.  * 17-22:16:12 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 18-22:14:38 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 18-22:14:40 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:40 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 18-22:14:40 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 18-22:14: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  * 18-22:15:03 (2925) [INFO] Checking if your system is up to date:  * 18-22:15:03 (3361) [INFO] Running: /usr/bin/yum clean all * 18-22:15:03 (3362) [INFO]  * 18-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:03 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 18-22:15:03 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 18-22:15:03 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 18-22:15:03 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 18-22:15:03 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 18-22:15:03 (3372) [INFO] : wp-toolkit-thirdparties * 18-22:15:03 (3372) [INFO] Cleaning up list of fastest mirrors * 18-22:15:03 (3382) [INFO]  * 18-22:15:03 (3361) [INFO] Running: /usr/bin/yum check-update * 18-22:15:03 (3362) [INFO]  * 18-22:15:03 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 18-22:15:04 (3372) [INFO] Determining fastest mirrors * 18-22:15:11 (3372) [INFO] * EA4: 185.15.22.168 * 18-22:15:11 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 18-22:15:11 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 18-22:15:11 (3372) [INFO] * epel: lon.mirror.rackspace.com * 18-22:15:29 (3372) [INFO]  * 18-22:15:29 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 18-22:15:29 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 18-22:15:29 (3382) [INFO]  * 18-22:15:29 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 18-22:15:29 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 18-22:15:29 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 18-22:15:29 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 18-22:15:30 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-18_22:15:30_modified_for_AlmaLinux_8.json * 18-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 18-22:15: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.  * 18-22:15:30 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 19-22:14:43 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 19-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 19-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 19-22:14: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  * 19-22:15:12 (2925) [INFO] Checking if your system is up to date:  * 19-22:15:12 (3361) [INFO] Running: /usr/bin/yum clean all * 19-22:15:12 (3362) [INFO]  * 19-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 19-22:15:12 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 19-22:15:12 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 19-22:15:12 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 19-22:15:12 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 19-22:15:12 (3372) [INFO] : wp-toolkit-thirdparties * 19-22:15:13 (3372) [INFO] Cleaning up list of fastest mirrors * 19-22:15:13 (3382) [INFO]  * 19-22:15:13 (3361) [INFO] Running: /usr/bin/yum check-update * 19-22:15:13 (3362) [INFO]  * 19-22:15:13 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 19-22:15:13 (3372) [INFO] Determining fastest mirrors * 19-22:15:18 (3372) [INFO] * EA4: 185.15.22.168 * 19-22:15:18 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 19-22:15:18 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 19-22:15:18 (3372) [INFO] * epel: mirrors.20i.com * 19-22:15:36 (3372) [INFO]  * 19-22:15:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 19-22:15:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 19-22:15:37 (3382) [INFO]  * 19-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 19-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 19-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 19-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 19-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-19_22:15:37_modified_for_AlmaLinux_8.json * 19-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 19-22:15: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.  * 19-22:15:38 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 20-22:13:59 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 20-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:01 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 20-22:14:01 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 20-22:14: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  * 20-22:14:24 (2925) [INFO] Checking if your system is up to date:  * 20-22:14:24 (3361) [INFO] Running: /usr/bin/yum clean all * 20-22:14:24 (3362) [INFO]  * 20-22:14:24 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 20-22:14:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 20-22:14:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 20-22:14:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 20-22:14:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 20-22:14:25 (3372) [INFO] : wp-toolkit-thirdparties * 20-22:14:25 (3372) [INFO] Cleaning up list of fastest mirrors * 20-22:14:25 (3382) [INFO]  * 20-22:14:25 (3361) [INFO] Running: /usr/bin/yum check-update * 20-22:14:25 (3362) [INFO]  * 20-22:14:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 20-22:14:25 (3372) [INFO] Determining fastest mirrors * 20-22:14:27 (3372) [INFO] * EA4: 185.15.22.168 * 20-22:14:27 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 20-22:14:27 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 20-22:14:27 (3372) [INFO] * epel: mirrors.20i.com * 20-22:14:44 (3372) [INFO]  * 20-22:14:44 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 20-22:14:44 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 20-22:14:44 (3382) [INFO]  * 20-22:14:44 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 20-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 20-22:14:44 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 20-22:14:44 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 20-22:14:45 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-20_22:14:45_modified_for_AlmaLinux_8.json * 20-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 20-22:14: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.  * 20-22:14:45 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 21-22:14:02 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 21-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 21-22:14:04 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 21-22:14: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  * 21-22:14:29 (2925) [INFO] Checking if your system is up to date:  * 21-22:14:29 (3361) [INFO] Running: /usr/bin/yum clean all * 21-22:14:29 (3362) [INFO]  * 21-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:30 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 21-22:14:30 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 21-22:14:30 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 21-22:14:30 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 21-22:14:30 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 21-22:14:30 (3372) [INFO] : wp-toolkit-thirdparties * 21-22:14:30 (3372) [INFO] Cleaning up list of fastest mirrors * 21-22:14:30 (3382) [INFO]  * 21-22:14:30 (3361) [INFO] Running: /usr/bin/yum check-update * 21-22:14:30 (3362) [INFO]  * 21-22:14:30 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 21-22:14:30 (3372) [INFO] Determining fastest mirrors * 21-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 21-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 21-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 21-22:14:32 (3372) [INFO] * epel: mirrors.20i.com * 21-22:14:50 (3372) [INFO]  * 21-22:14:50 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 21-22:14:50 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 21-22:14:50 (3382) [INFO]  * 21-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 21-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 21-22:14:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 21-22:14:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 21-22:14:51 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-21_22:14:51_modified_for_AlmaLinux_8.json * 21-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 21-22:14: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.  * 21-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 22-22:15:15 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 22-22:15:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:16 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 22-22:15:16 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 22-22:15: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  * 22-22:15:41 (2925) [INFO] Checking if your system is up to date:  * 22-22:15:41 (3361) [INFO] Running: /usr/bin/yum clean all * 22-22:15:41 (3362) [INFO]  * 22-22:15:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 22-22:15:41 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 22-22:15:41 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 22-22:15:41 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 22-22:15:41 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 22-22:15:41 (3372) [INFO] : wp-toolkit-thirdparties * 22-22:15:42 (3372) [INFO] Cleaning up list of fastest mirrors * 22-22:15:42 (3382) [INFO]  * 22-22:15:42 (3361) [INFO] Running: /usr/bin/yum check-update * 22-22:15:42 (3362) [INFO]  * 22-22:15:42 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 22-22:15:42 (3372) [INFO] Determining fastest mirrors * 22-22:15:45 (3372) [INFO] * EA4: 185.15.22.168 * 22-22:15:45 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 22-22:15:45 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 22-22:15:45 (3372) [INFO] * epel: creeperhost.mm.fcix.net * 22-22:16:04 (3372) [INFO]  * 22-22:16:04 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 22-22:16:04 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 22-22:16:04 (3382) [INFO]  * 22-22:16:04 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 22-22:16:04 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 22-22:16:04 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 22-22:16:04 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 22-22:16:05 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-22_22:16:05_modified_for_AlmaLinux_8.json * 22-22:16:05 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 22-22:16: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.  * 22-22:16:05 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 23-22:14:52 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 23-22:14:55 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:55 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 23-22:14:55 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 23-22:14: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  * 23-22:15:32 (2925) [INFO] Checking if your system is up to date:  * 23-22:15:32 (3361) [INFO] Running: /usr/bin/yum clean all * 23-22:15:32 (3362) [INFO]  * 23-22:15:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:15:33 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 23-22:15:33 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 23-22:15:33 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 23-22:15:33 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 23-22:15:33 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 23-22:15:33 (3372) [INFO] : wp-toolkit-thirdparties * 23-22:15:33 (3372) [INFO] Cleaning up list of fastest mirrors * 23-22:15:33 (3382) [INFO]  * 23-22:15:33 (3361) [INFO] Running: /usr/bin/yum check-update * 23-22:15:33 (3362) [INFO]  * 23-22:15:33 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 23-22:15:34 (3372) [INFO] Determining fastest mirrors * 23-22:15:37 (3372) [INFO] * EA4: 185.15.22.168 * 23-22:15:37 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 23-22:15:37 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 23-22:15:37 (3372) [INFO] * epel: lon.mirror.rackspace.com * 23-22:15:57 (3372) [INFO]  * 23-22:15:57 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 23-22:15:57 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 23-22:15:57 (3382) [INFO]  * 23-22:15:57 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 23-22:15:57 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 23-22:15:57 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 23-22:15:57 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 23-22:15:58 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-23_22:15:58_modified_for_AlmaLinux_8.json * 23-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 23-22:15: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.  * 23-22:15:58 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 24-22:14:09 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 24-22:14:11 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:11 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 24-22:14:11 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 24-22:14:11 (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-22:14:35 (2925) [INFO] Checking if your system is up to date:  * 24-22:14:35 (3361) [INFO] Running: /usr/bin/yum clean all * 24-22:14:35 (3362) [INFO]  * 24-22:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:36 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 24-22:14:36 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 24-22:14:36 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 24-22:14:36 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 24-22:14:36 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 24-22:14:36 (3372) [INFO] : wp-toolkit-thirdparties * 24-22:14:36 (3372) [INFO] Cleaning up list of fastest mirrors * 24-22:14:36 (3382) [INFO]  * 24-22:14:36 (3361) [INFO] Running: /usr/bin/yum check-update * 24-22:14:36 (3362) [INFO]  * 24-22:14:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 24-22:14:36 (3372) [INFO] Determining fastest mirrors * 24-22:14:39 (3372) [INFO] * EA4: 185.15.22.168 * 24-22:14:39 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 24-22:14:39 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 24-22:14:39 (3372) [INFO] * epel: lon.mirror.rackspace.com * 24-22:14:58 (3372) [INFO]  * 24-22:14:58 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 24-22:14:58 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 24-22:14:58 (3382) [INFO]  * 24-22:14:58 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 24-22:14:58 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 24-22:14:58 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 24-22:14:58 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 24-22:14:59 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-24_22:14:59_modified_for_AlmaLinux_8.json * 24-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 24-22:14: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.  * 24-22:14:59 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 25-22:15:17 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 25-22:15:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:15:21 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 25-22:15:21 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 25-22:15: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  * 25-22:15:49 (2925) [INFO] Checking if your system is up to date:  * 25-22:15:49 (3361) [INFO] Running: /usr/bin/yum clean all * 25-22:15:49 (3362) [INFO]  * 25-22:15:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:49 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 25-22:15:49 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 25-22:15:49 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 25-22:15:49 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 25-22:15:49 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 25-22:15:49 (3372) [INFO] : wp-toolkit-thirdparties * 25-22:15:49 (3372) [INFO] Cleaning up list of fastest mirrors * 25-22:15:49 (3382) [INFO]  * 25-22:15:49 (3361) [INFO] Running: /usr/bin/yum check-update * 25-22:15:49 (3362) [INFO]  * 25-22:15:49 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 25-22:15:50 (3372) [INFO] Determining fastest mirrors * 25-22:15:55 (3372) [INFO] * EA4: 185.15.22.168 * 25-22:15:55 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 25-22:15:55 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 25-22:15:55 (3372) [INFO] * epel: lon.mirror.rackspace.com * 25-22:16:13 (3372) [INFO]  * 25-22:16:13 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 25-22:16:13 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 25-22:16:13 (3382) [INFO]  * 25-22:16:13 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 25-22:16:13 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 25-22:16:13 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 25-22:16:13 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 25-22:16:14 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-25_22:16:14_modified_for_AlmaLinux_8.json * 25-22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 25-22:16: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.  * 25-22:16:14 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 26-22:14:54 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 26-22:14:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:57 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 26-22:14:57 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 26-22:14: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  * 26-22:15:25 (2925) [INFO] Checking if your system is up to date:  * 26-22:15:25 (3361) [INFO] Running: /usr/bin/yum clean all * 26-22:15:25 (3362) [INFO]  * 26-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:25 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 26-22:15:25 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 26-22:15:25 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 26-22:15:25 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 26-22:15:25 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 26-22:15:25 (3372) [INFO] : wp-toolkit-thirdparties * 26-22:15:25 (3372) [INFO] Cleaning up list of fastest mirrors * 26-22:15:25 (3382) [INFO]  * 26-22:15:25 (3361) [INFO] Running: /usr/bin/yum check-update * 26-22:15:25 (3362) [INFO]  * 26-22:15:25 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 26-22:15:26 (3372) [INFO] Determining fastest mirrors * 26-22:15:29 (3372) [INFO] * EA4: 185.15.22.168 * 26-22:15:29 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 26-22:15:29 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 26-22:15:29 (3372) [INFO] * epel: mirrors.20i.com * 26-22:15:47 (3372) [INFO]  * 26-22:15:47 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 26-22:15:47 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 26-22:15:47 (3382) [INFO]  * 26-22:15:47 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 26-22:15:47 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 26-22:15:47 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 26-22:15:47 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 26-22:15:48 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-26_22:15:48_modified_for_AlmaLinux_8.json * 26-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 26-22:15: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.  * 26-22:15:49 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 27-22:14:12 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 27-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:13 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 27-22:14:13 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 27-22:14:13 (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-22:14:38 (2925) [INFO] Checking if your system is up to date:  * 27-22:14:38 (3361) [INFO] Running: /usr/bin/yum clean all * 27-22:14:38 (3362) [INFO]  * 27-22:14:38 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:38 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 27-22:14:38 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 27-22:14:38 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 27-22:14:38 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 27-22:14:38 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 27-22:14:38 (3372) [INFO] : wp-toolkit-thirdparties * 27-22:14:39 (3372) [INFO] Cleaning up list of fastest mirrors * 27-22:14:39 (3382) [INFO]  * 27-22:14:39 (3361) [INFO] Running: /usr/bin/yum check-update * 27-22:14:39 (3362) [INFO]  * 27-22:14:39 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 27-22:14:39 (3372) [INFO] Determining fastest mirrors * 27-22:14:43 (3372) [INFO] * EA4: 185.15.22.168 * 27-22:14:43 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 27-22:14:43 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 27-22:14:43 (3372) [INFO] * epel: mirrors.20i.com * 27-22:15:02 (3372) [INFO]  * 27-22:15:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 27-22:15:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 27-22:15:02 (3382) [INFO]  * 27-22:15:02 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 27-22:15:02 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 27-22:15:02 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 27-22:15:02 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 27-22:15:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-27_22:15:03_modified_for_AlmaLinux_8.json * 27-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 27-22:15: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-22:15:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 28-22:14:41 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 28-22:14:44 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:44 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 28-22:14:44 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 28-22:14: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  * 28-22:15:17 (2925) [INFO] Checking if your system is up to date:  * 28-22:15:17 (3361) [INFO] Running: /usr/bin/yum clean all * 28-22:15:17 (3362) [INFO]  * 28-22:15:17 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:18 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 28-22:15:18 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 28-22:15:18 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 28-22:15:18 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 28-22:15:18 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 28-22:15:18 (3372) [INFO] : wp-toolkit-thirdparties * 28-22:15:18 (3372) [INFO] Cleaning up list of fastest mirrors * 28-22:15:18 (3382) [INFO]  * 28-22:15:18 (3361) [INFO] Running: /usr/bin/yum check-update * 28-22:15:18 (3362) [INFO]  * 28-22:15:18 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 28-22:15:18 (3372) [INFO] Determining fastest mirrors * 28-22:15:23 (3372) [INFO] * EA4: 185.15.22.168 * 28-22:15:23 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 28-22:15:23 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 28-22:15:23 (3372) [INFO] * epel: lon.mirror.rackspace.com * 28-22:15:41 (3372) [INFO]  * 28-22:15:41 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 28-22:15:41 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 28-22:15:41 (3382) [INFO]  * 28-22:15:41 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 28-22:15:41 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 28-22:15:41 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 28-22:15:41 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 28-22:15:42 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-02-28_22:15:42_modified_for_AlmaLinux_8.json * 28-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 28-22:15: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.  * 28-22:15:42 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 01-22:14:09 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 01-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:10 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 01-22:14:10 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 01-22:14: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  * 01-22:14:35 (2925) [INFO] Checking if your system is up to date:  * 01-22:14:35 (3361) [INFO] Running: /usr/bin/yum clean all * 01-22:14:35 (3362) [INFO]  * 01-22:14:35 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:35 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 01-22:14:35 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 01-22:14:35 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 01-22:14:35 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 01-22:14:35 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 01-22:14:35 (3372) [INFO] : wp-toolkit-thirdparties * 01-22:14:36 (3372) [INFO] Cleaning up list of fastest mirrors * 01-22:14:36 (3382) [INFO]  * 01-22:14:36 (3361) [INFO] Running: /usr/bin/yum check-update * 01-22:14:36 (3362) [INFO]  * 01-22:14:36 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 01-22:14:36 (3372) [INFO] Determining fastest mirrors * 01-22:14:40 (3372) [INFO] * EA4: 185.15.22.168 * 01-22:14:40 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 01-22:14:40 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 01-22:14:40 (3372) [INFO] * epel: lon.mirror.rackspace.com * 01-22:15:02 (3372) [INFO]  * 01-22:15:02 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 01-22:15:02 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 01-22:15:03 (3382) [INFO]  * 01-22:15:03 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 01-22:15:03 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 01-22:15:03 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 01-22:15:03 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 01-22:15:03 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-01_22:15:03_modified_for_AlmaLinux_8.json * 01-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 01-22:15: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.  * 01-22:15:03 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 02-22:14:29 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 02-22:14:30 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:30 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 02-22:14:30 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 02-22:14:30 (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-22:14:55 (2925) [INFO] Checking if your system is up to date:  * 02-22:14:55 (3361) [INFO] Running: /usr/bin/yum clean all * 02-22:14:55 (3362) [INFO]  * 02-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:55 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 02-22:14:55 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 02-22:14:55 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 02-22:14:55 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 02-22:14:55 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 02-22:14:55 (3372) [INFO] : wp-toolkit-thirdparties * 02-22:14:55 (3372) [INFO] Cleaning up list of fastest mirrors * 02-22:14:55 (3382) [INFO]  * 02-22:14:55 (3361) [INFO] Running: /usr/bin/yum check-update * 02-22:14:55 (3362) [INFO]  * 02-22:14:55 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 02-22:14:56 (3372) [INFO] Determining fastest mirrors * 02-22:14:59 (3372) [INFO] * EA4: 185.15.22.168 * 02-22:14:59 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 02-22:14:59 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 02-22:14:59 (3372) [INFO] * epel: creeperhost.mm.fcix.net * 02-22:15:17 (3372) [INFO]  * 02-22:15:17 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 02-22:15:17 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 02-22:15:18 (3382) [INFO]  * 02-22:15:18 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 02-22:15:18 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 02-22:15:18 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 02-22:15:18 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 02-22:15:18 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-02_22:15:18_modified_for_AlmaLinux_8.json * 02-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 02-22:15: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-22:15:19 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 03-22:14:05 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 03-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:07 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 03-22:14:07 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 03-22:14: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  * 03-22:14:32 (2925) [INFO] Checking if your system is up to date:  * 03-22:14:32 (3361) [INFO] Running: /usr/bin/yum clean all * 03-22:14:32 (3362) [INFO]  * 03-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:32 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 03-22:14:32 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 03-22:14:32 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 03-22:14:32 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 03-22:14:32 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 03-22:14:32 (3372) [INFO] : wp-toolkit-thirdparties * 03-22:14:32 (3372) [INFO] Cleaning up list of fastest mirrors * 03-22:14:32 (3382) [INFO]  * 03-22:14:32 (3361) [INFO] Running: /usr/bin/yum check-update * 03-22:14:32 (3362) [INFO]  * 03-22:14:32 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 03-22:14:33 (3372) [INFO] Determining fastest mirrors * 03-22:14:36 (3372) [INFO] * EA4: 185.15.22.168 * 03-22:14:36 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 03-22:14:36 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 03-22:14:36 (3372) [INFO] * epel: mirrors.20i.com * 03-22:14:54 (3372) [INFO]  * 03-22:14:54 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 03-22:14:54 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 03-22:14:55 (3382) [INFO]  * 03-22:14:55 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 03-22:14:55 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 03-22:14:55 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 03-22:14:55 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 03-22:14:55 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-03_22:14:55_modified_for_AlmaLinux_8.json * 03-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 03-22:14:56 (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-22:14:56 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 04-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 04-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 04-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 04-22:14: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  * 04-22:15:10 (2925) [INFO] Checking if your system is up to date:  * 04-22:15:10 (3361) [INFO] Running: /usr/bin/yum clean all * 04-22:15:10 (3362) [INFO]  * 04-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:10 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 04-22:15:10 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 04-22:15:10 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 04-22:15:10 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 04-22:15:10 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 04-22:15:10 (3372) [INFO] : wp-toolkit-thirdparties * 04-22:15:10 (3372) [INFO] Cleaning up list of fastest mirrors * 04-22:15:10 (3382) [INFO]  * 04-22:15:10 (3361) [INFO] Running: /usr/bin/yum check-update * 04-22:15:10 (3362) [INFO]  * 04-22:15:10 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 04-22:15:10 (3372) [INFO] Determining fastest mirrors * 04-22:15:19 (3372) [INFO] * EA4: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 04-22:15:19 (3372) [INFO] * epel: cdn.centos.no * 04-22:15:37 (3372) [INFO]  * 04-22:15:37 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 04-22:15:37 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 04-22:15:37 (3382) [INFO]  * 04-22:15:37 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 04-22:15:37 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 04-22:15:37 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 04-22:15:37 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 04-22:15:38 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-04_22:15:38_modified_for_AlmaLinux_8.json * 04-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 04-22:15: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.  * 04-22:15:38 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 05-22:14:44 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 05-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:46 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 05-22:14:46 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 05-22:14: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  * 05-22:15:11 (2925) [INFO] Checking if your system is up to date:  * 05-22:15:11 (3361) [INFO] Running: /usr/bin/yum clean all * 05-22:15:11 (3362) [INFO]  * 05-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:12 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 05-22:15:12 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 05-22:15:12 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 05-22:15:12 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 05-22:15:12 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 05-22:15:12 (3372) [INFO] : wp-toolkit-thirdparties * 05-22:15:12 (3372) [INFO] Cleaning up list of fastest mirrors * 05-22:15:12 (3382) [INFO]  * 05-22:15:12 (3361) [INFO] Running: /usr/bin/yum check-update * 05-22:15:12 (3362) [INFO]  * 05-22:15:12 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 05-22:15:12 (3372) [INFO] Determining fastest mirrors * 05-22:15:18 (3372) [INFO] * EA4: 185.15.22.168 * 05-22:15:18 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 05-22:15:18 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 05-22:15:18 (3372) [INFO] * epel: lon.mirror.rackspace.com * 05-22:15:36 (3372) [INFO]  * 05-22:15:36 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 05-22:15:36 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 05-22:15:36 (3382) [INFO]  * 05-22:15:36 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 05-22:15:36 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 05-22:15:36 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 05-22:15:36 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 05-22:15:37 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-05_22:15:37_modified_for_AlmaLinux_8.json * 05-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 05-22:15: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.  * 05-22:15:37 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 06-22:14:00 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 06-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 06-22:14:04 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 06-22:14: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  * 06-22:14:27 (2925) [INFO] Checking if your system is up to date:  * 06-22:14:27 (3361) [INFO] Running: /usr/bin/yum clean all * 06-22:14:27 (3362) [INFO]  * 06-22:14:27 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:27 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 06-22:14:27 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 06-22:14:27 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 06-22:14:27 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 06-22:14:27 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 06-22:14:27 (3372) [INFO] : wp-toolkit-thirdparties * 06-22:14:28 (3372) [INFO] Cleaning up list of fastest mirrors * 06-22:14:28 (3382) [INFO]  * 06-22:14:28 (3361) [INFO] Running: /usr/bin/yum check-update * 06-22:14:28 (3362) [INFO]  * 06-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 06-22:14:28 (3372) [INFO] Determining fastest mirrors * 06-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 06-22:14:32 (3372) [INFO] * epel: cdn.centos.no * 06-22:14:49 (3372) [INFO]  * 06-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 06-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 06-22:14:50 (3382) [INFO]  * 06-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 06-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 06-22:14:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 06-22:14:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 06-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-06_22:14:50_modified_for_AlmaLinux_8.json * 06-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 06-22:14: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.  * 06-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 07-22:14:03 (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.  * 07-22:14:04 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 07-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:06 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 07-22:14:06 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 07-22:14: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-22:14:41 (2925) [INFO] Checking if your system is up to date:  * 07-22:14:41 (3361) [INFO] Running: /usr/bin/yum clean all * 07-22:14:41 (3362) [INFO]  * 07-22:14:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:41 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 07-22:14:41 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 07-22:14:41 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 07-22:14:41 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 07-22:14:41 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 07-22:14:41 (3372) [INFO] : wp-toolkit-thirdparties * 07-22:14:41 (3372) [INFO] Cleaning up list of fastest mirrors * 07-22:14:41 (3382) [INFO]  * 07-22:14:41 (3361) [INFO] Running: /usr/bin/yum check-update * 07-22:14:41 (3362) [INFO]  * 07-22:14:41 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 07-22:14:41 (3372) [INFO] Determining fastest mirrors * 07-22:14:44 (3372) [INFO] * EA4: 185.15.22.168 * 07-22:14:44 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 07-22:14:44 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 07-22:14:44 (3372) [INFO] * epel: cdn.centos.no * 07-22:15:20 (3372) [INFO]  * 07-22:15:20 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 07-22:15:20 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 07-22:15:20 (3382) [INFO]  * 07-22:15:20 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 07-22:15:20 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 07-22:15:20 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 07-22:15:20 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 07-22:15:21 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-07_22:15:21_modified_for_AlmaLinux_8.json * 07-22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 07-22:15: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.  * 07-22:15:21 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 08-22:14:02 (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-22:14:02 (2504) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 community server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8.  * 08-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-connectors-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:04 (3029) [WARN] Unsupported YUM repo enabled 'mysql-tools-community' without packages installed from /etc/yum.repos.d/mysql-community.repo * 08-22:14:04 (3018) [ERROR] 6 package(s) installed from unsupported YUM repo 'mysql57-community' from /etc/yum.repos.d/mysql-community.repo * 08-22:14: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  * 08-22:14:27 (2925) [INFO] Checking if your system is up to date:  * 08-22:14:27 (3361) [INFO] Running: /usr/bin/yum clean all * 08-22:14:27 (3362) [INFO]  * 08-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:28 (3372) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 08-22:14:28 (3372) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 08-22:14:28 (3372) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 08-22:14:28 (3372) [INFO] : mysql-connectors-community mysql-tools-community * 08-22:14:28 (3372) [INFO] : mysql57-community updates wp-toolkit-cpanel * 08-22:14:28 (3372) [INFO] : wp-toolkit-thirdparties * 08-22:14:28 (3372) [INFO] Cleaning up list of fastest mirrors * 08-22:14:28 (3382) [INFO]  * 08-22:14:28 (3361) [INFO] Running: /usr/bin/yum check-update * 08-22:14:28 (3362) [INFO]  * 08-22:14:28 (3372) [INFO] Loaded plugins: fastestmirror, universal-hooks * 08-22:14:28 (3372) [INFO] Determining fastest mirrors * 08-22:14:32 (3372) [INFO] * EA4: 185.15.22.168 * 08-22:14:32 (3372) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 08-22:14:32 (3372) [INFO] * cpanel-plugins: 185.15.22.168 * 08-22:14:32 (3372) [INFO] * epel: cdn.centos.no * 08-22:14:49 (3372) [INFO]  * 08-22:14:49 (3372) [INFO] kernel.x86_64 3.10.0-1160.83.1.el7 updates * 08-22:14:49 (3372) [INFO] kmod-libs.x86_64 20-28.el7 base  * 08-22:14:50 (3382) [INFO]  * 08-22:14:50 (2928) [WARN] Your system is not up to date please run: /usr/bin/yum update * 08-22:14:50 (2504) [WARN] *** Elevation Blocker detected: *** System is not up to date  * 08-22:14:50 (2804) [INFO] Checking EasyApache profile compatibility with Almalinux 8. * 08-22:14:50 (1448) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 * 08-22:14:50 (1469) [INFO] Backed up EA4 profile to /etc/cpanel/ea4/profiles/custom/current_state_at_2023-03-08_22:14:50_modified_for_AlmaLinux_8.json * 08-22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime  * 08-22:14: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.  * 08-22:14:51 (570) [WARN] Please fix the detected issues before performing the elevation process.  * 2023-03-09 22:20:04 (2749) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-09 22:20:12 (3566) [INFO] Checking if your system is up to date: * 2023-03-09 22:20:12 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-09 22:20:12 (4079) [INFO] * 2023-03-09 22:20:12 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-09 22:20:12 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-09 22:20:12 (4093) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-09 22:20:12 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-09 22:20:12 (4093) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-09 22:20:12 (4093) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-09 22:20:12 (4093) [INFO] : wp-toolkit-thirdparties * 2023-03-09 22:20:12 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-09 22:20:12 (4093) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-09 22:20:12 (4110) [INFO] * 2023-03-09 22:20:12 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-09 22:20:12 (4079) [INFO] * 2023-03-09 22:20:32 (4093) [INFO] * 2023-03-09 22:20:32 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-09 22:20:32 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-09 22:20:33 (4110) [INFO] * 2023-03-09 22:20:33 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-09 22:20:33 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-09 22:20:33 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-09 22:20:33 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/adztsQo9S9/ea_profile.json * 2023-03-09 22:20:33 (1694) [INFO] Backed up EA4 profile to /tmp/adztsQo9S9/ea_profile.json * 2023-03-09 22:20:33 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-09 22:20:33 (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 22:20:34 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-10 22:13:59 (2749) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-10 22:14:22 (3566) [INFO] Checking if your system is up to date: * 2023-03-10 22:14:22 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-10 22:14:22 (4079) [INFO] * 2023-03-10 22:14:22 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-10 22:14:22 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-10 22:14:22 (4093) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-10 22:14:22 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-10 22:14:22 (4093) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-10 22:14:22 (4093) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-10 22:14:22 (4093) [INFO] : wp-toolkit-thirdparties * 2023-03-10 22:14:22 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-10 22:14:22 (4093) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-10 22:14:22 (4110) [INFO] * 2023-03-10 22:14:22 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-10 22:14:22 (4079) [INFO] * 2023-03-10 22:14:45 (4093) [INFO] * 2023-03-10 22:14:45 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-10 22:14:45 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-10 22:14:45 (4110) [INFO] * 2023-03-10 22:14:45 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-10 22:14:45 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-10 22:14:45 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-10 22:14:45 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nn7o64Nk4P/ea_profile.json * 2023-03-10 22:14:46 (1694) [INFO] Backed up EA4 profile to /tmp/nn7o64Nk4P/ea_profile.json * 2023-03-10 22:14:46 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-10 22:14:46 (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 22:14:46 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-11 22:14:52 (2749) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-11 22:15:16 (3566) [INFO] Checking if your system is up to date: * 2023-03-11 22:15:16 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-11 22:15:16 (4079) [INFO] * 2023-03-11 22:15:16 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-11 22:15:17 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-11 22:15:17 (4093) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-11 22:15:17 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-11 22:15:17 (4093) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-11 22:15:17 (4093) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-11 22:15:17 (4093) [INFO] : wp-toolkit-thirdparties * 2023-03-11 22:15:17 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-11 22:15:17 (4093) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-11 22:15:17 (4110) [INFO] * 2023-03-11 22:15:17 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-11 22:15:17 (4079) [INFO] * 2023-03-11 22:15:39 (4093) [INFO] * 2023-03-11 22:15:39 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-11 22:15:39 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-11 22:15:39 (4110) [INFO] * 2023-03-11 22:15:39 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-11 22:15:39 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-11 22:15:39 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-11 22:15:39 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6_xFbrwMZ9/ea_profile.json * 2023-03-11 22:15:40 (1694) [INFO] Backed up EA4 profile to /tmp/6_xFbrwMZ9/ea_profile.json * 2023-03-11 22:15:40 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-11 22:15:40 (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 22:15:40 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-12 22:14:52 (2749) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-12 22:15:15 (3566) [INFO] Checking if your system is up to date: * 2023-03-12 22:15:15 (4078) [INFO] Running: /usr/bin/yum clean all * 2023-03-12 22:15:15 (4079) [INFO] * 2023-03-12 22:15:15 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-12 22:15:15 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-12 22:15:15 (4093) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-12 22:15:15 (4093) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-12 22:15:15 (4093) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-12 22:15:15 (4093) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-12 22:15:15 (4093) [INFO] : wp-toolkit-thirdparties * 2023-03-12 22:15:16 (4093) [INFO] Cleaning up list of fastest mirrors * 2023-03-12 22:15:16 (4093) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-12 22:15:16 (4110) [INFO] * 2023-03-12 22:15:16 (4078) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-12 22:15:16 (4079) [INFO] * 2023-03-12 22:15:39 (4093) [INFO] * 2023-03-12 22:15:39 (4093) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-12 22:15:39 (4093) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-12 22:15:39 (4110) [INFO] * 2023-03-12 22:15:39 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-12 22:15:39 (2749) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-12 22:15:39 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-12 22:15:39 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bIFUjKtSTG/ea_profile.json * 2023-03-12 22:15:40 (1694) [INFO] Backed up EA4 profile to /tmp/bIFUjKtSTG/ea_profile.json * 2023-03-12 22:15:40 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-12 22:15:40 (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 22:15:40 (713) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-13 22:14:14 (368) [INFO] Self-update of script version 5 requested. * 2023-03-13 22:14:14 (373) [INFO] Newer version of script found. Downloading. * 2023-03-13 22:14:14 (382) [INFO] Script update to version 6 successful. * 2023-03-13 22:14:15 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-13 22:14:36 (3638) [INFO] Checking if your system is up to date: * 2023-03-13 22:14:36 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-13 22:14:36 (4151) [INFO] * 2023-03-13 22:14:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-13 22:14:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-13 22:14:37 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-13 22:14:37 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-13 22:14:37 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-13 22:14:37 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-13 22:14:37 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-13 22:14:37 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-13 22:14:37 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-13 22:14:37 (4182) [INFO] * 2023-03-13 22:14:37 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-13 22:14:37 (4151) [INFO] * 2023-03-13 22:14:57 (4165) [INFO] * 2023-03-13 22:14:57 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-13 22:14:57 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-13 22:14:58 (4182) [INFO] * 2023-03-13 22:14:58 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-13 22:14:58 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-13 22:14:58 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-13 22:14:58 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rI1YhzNr4B/ea_profile.json * 2023-03-13 22:14:58 (1765) [INFO] Backed up EA4 profile to /tmp/rI1YhzNr4B/ea_profile.json * 2023-03-13 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-13 22:14: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-03-13 22:14:59 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-14 22:13:59 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-14 22:14:21 (3638) [INFO] Checking if your system is up to date: * 2023-03-14 22:14:21 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-14 22:14:21 (4151) [INFO] * 2023-03-14 22:14:21 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-14 22:14:22 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-14 22:14:22 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-14 22:14:22 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-14 22:14:22 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-14 22:14:22 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-14 22:14:22 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-14 22:14:22 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-14 22:14:22 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-14 22:14:22 (4182) [INFO] * 2023-03-14 22:14:22 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-14 22:14:22 (4151) [INFO] * 2023-03-14 22:14:41 (4165) [INFO] * 2023-03-14 22:14:41 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-14 22:14:41 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-14 22:14:42 (4182) [INFO] * 2023-03-14 22:14:42 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-14 22:14:42 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-14 22:14:42 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-14 22:14:42 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dJjRkTsC4t/ea_profile.json * 2023-03-14 22:14:42 (1765) [INFO] Backed up EA4 profile to /tmp/dJjRkTsC4t/ea_profile.json * 2023-03-14 22:14:42 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-14 22:14:42 (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 22:14:43 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-15 22:14:03 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-15 22:14:26 (3638) [INFO] Checking if your system is up to date: * 2023-03-15 22:14:26 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-15 22:14:26 (4151) [INFO] * 2023-03-15 22:14:26 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-15 22:14:26 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-15 22:14:26 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-15 22:14:26 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-15 22:14:26 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-15 22:14:26 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-15 22:14:26 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-15 22:14:26 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-15 22:14:26 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-15 22:14:26 (4182) [INFO] * 2023-03-15 22:14:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-15 22:14:26 (4151) [INFO] * 2023-03-15 22:14:48 (4165) [INFO] * 2023-03-15 22:14:48 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-15 22:14:48 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-15 22:14:48 (4182) [INFO] * 2023-03-15 22:14:48 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-15 22:14:48 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-15 22:14:48 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-15 22:14:48 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Mk7DZV02CS/ea_profile.json * 2023-03-15 22:14:49 (1765) [INFO] Backed up EA4 profile to /tmp/Mk7DZV02CS/ea_profile.json * 2023-03-15 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-15 22:14:49 (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 22:14:49 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-16 22:13:56 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-16 22:14:18 (3638) [INFO] Checking if your system is up to date: * 2023-03-16 22:14:18 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-16 22:14:18 (4151) [INFO] * 2023-03-16 22:14:18 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-16 22:14:18 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-16 22:14:18 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-16 22:14:18 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-16 22:14:18 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-16 22:14:18 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-16 22:14:18 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-16 22:14:19 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-16 22:14:19 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-16 22:14:19 (4182) [INFO] * 2023-03-16 22:14:19 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-16 22:14:19 (4151) [INFO] * 2023-03-16 22:14:37 (4165) [INFO] * 2023-03-16 22:14:37 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-16 22:14:37 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-16 22:14:38 (4182) [INFO] * 2023-03-16 22:14:38 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-16 22:14:38 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-16 22:14:38 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-16 22:14:38 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wuLgF_sU34/ea_profile.json * 2023-03-16 22:14:38 (1765) [INFO] Backed up EA4 profile to /tmp/wuLgF_sU34/ea_profile.json * 2023-03-16 22:14:38 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-16 22:14:39 (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 22:14:39 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-17 22:13:54 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-17 22:14:16 (3638) [INFO] Checking if your system is up to date: * 2023-03-17 22:14:16 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-17 22:14:16 (4151) [INFO] * 2023-03-17 22:14:16 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-17 22:14:16 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-17 22:14:16 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-17 22:14:16 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-17 22:14:16 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-17 22:14:16 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-17 22:14:16 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-17 22:14:16 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-17 22:14:16 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-17 22:14:16 (4182) [INFO] * 2023-03-17 22:14:16 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-17 22:14:16 (4151) [INFO] * 2023-03-17 22:14:36 (4165) [INFO] * 2023-03-17 22:14:36 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-17 22:14:36 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-17 22:14:36 (4182) [INFO] * 2023-03-17 22:14:36 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-17 22:14:36 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-17 22:14:36 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-17 22:14:36 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AMVc3bDMhS/ea_profile.json * 2023-03-17 22:14:37 (1765) [INFO] Backed up EA4 profile to /tmp/AMVc3bDMhS/ea_profile.json * 2023-03-17 22:14:37 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-17 22:14:37 (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 22:14:37 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-18 22:14:58 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-18 22:15:19 (3638) [INFO] Checking if your system is up to date: * 2023-03-18 22:15:19 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-18 22:15:19 (4151) [INFO] * 2023-03-18 22:15:19 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-18 22:15:19 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-18 22:15:19 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-18 22:15:19 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-18 22:15:19 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-18 22:15:19 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-18 22:15:19 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-18 22:15:20 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-18 22:15:20 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-18 22:15:20 (4182) [INFO] * 2023-03-18 22:15:20 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-18 22:15:20 (4151) [INFO] * 2023-03-18 22:15:43 (4165) [INFO] * 2023-03-18 22:15:43 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-18 22:15:43 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-18 22:15:43 (4182) [INFO] * 2023-03-18 22:15:43 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-18 22:15:43 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-18 22:15:43 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-18 22:15:43 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iSG_gExVzY/ea_profile.json * 2023-03-18 22:15:44 (1765) [INFO] Backed up EA4 profile to /tmp/iSG_gExVzY/ea_profile.json * 2023-03-18 22:15:44 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-18 22:15:44 (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 22:15:44 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-19 22:14:52 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-19 22:15:17 (3638) [INFO] Checking if your system is up to date: * 2023-03-19 22:15:17 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-19 22:15:17 (4151) [INFO] * 2023-03-19 22:15:17 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-19 22:15:17 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-19 22:15:17 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-19 22:15:17 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-19 22:15:17 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-19 22:15:17 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-19 22:15:17 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-19 22:15:17 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-19 22:15:17 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-19 22:15:17 (4182) [INFO] * 2023-03-19 22:15:17 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-19 22:15:17 (4151) [INFO] * 2023-03-19 22:15:44 (4165) [INFO] * 2023-03-19 22:15:44 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-19 22:15:44 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-19 22:15:44 (4182) [INFO] * 2023-03-19 22:15:44 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-19 22:15:44 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-19 22:15:44 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-19 22:15:44 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PubmY1843A/ea_profile.json * 2023-03-19 22:15:44 (1765) [INFO] Backed up EA4 profile to /tmp/PubmY1843A/ea_profile.json * 2023-03-19 22:15:44 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-19 22:15:45 (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 22:15:45 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-20 22:14:12 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-20 22:14:35 (3638) [INFO] Checking if your system is up to date: * 2023-03-20 22:14:35 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-20 22:14:35 (4151) [INFO] * 2023-03-20 22:14:35 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-20 22:14:35 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-20 22:14:35 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-20 22:14:35 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-20 22:14:35 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-20 22:14:35 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-20 22:14:35 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-20 22:14:35 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-20 22:14:35 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-20 22:14:35 (4182) [INFO] * 2023-03-20 22:14:35 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-20 22:14:35 (4151) [INFO] * 2023-03-20 22:14:55 (4165) [INFO] * 2023-03-20 22:14:55 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-20 22:14:55 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-20 22:14:55 (4182) [INFO] * 2023-03-20 22:14:55 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-20 22:14:55 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-20 22:14:55 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-20 22:14:55 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W2dpapv8ha/ea_profile.json * 2023-03-20 22:14:56 (1765) [INFO] Backed up EA4 profile to /tmp/W2dpapv8ha/ea_profile.json * 2023-03-20 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-20 22:14: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-20 22:14:56 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-21 22:14:02 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-21 22:14:24 (3638) [INFO] Checking if your system is up to date: * 2023-03-21 22:14:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-21 22:14:24 (4151) [INFO] * 2023-03-21 22:14:24 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-21 22:14:24 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-21 22:14:24 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-21 22:14:24 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-21 22:14:24 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-21 22:14:24 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-21 22:14:24 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-21 22:14:24 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-21 22:14:24 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-21 22:14:24 (4182) [INFO] * 2023-03-21 22:14:24 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-21 22:14:24 (4151) [INFO] * 2023-03-21 22:14:46 (4165) [INFO] * 2023-03-21 22:14:46 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-21 22:14:46 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-21 22:14:46 (4182) [INFO] * 2023-03-21 22:14:46 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-21 22:14:46 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-21 22:14:46 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-21 22:14:46 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SJU2cMA6KM/ea_profile.json * 2023-03-21 22:14:47 (1765) [INFO] Backed up EA4 profile to /tmp/SJU2cMA6KM/ea_profile.json * 2023-03-21 22:14:47 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-21 22:14:47 (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 22:14:47 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-22 22:14:37 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-22 22:15:00 (3638) [INFO] Checking if your system is up to date: * 2023-03-22 22:15:00 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-22 22:15:00 (4151) [INFO] * 2023-03-22 22:15:00 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-22 22:15:00 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-22 22:15:00 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-22 22:15:00 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-22 22:15:00 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-22 22:15:00 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-22 22:15:00 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-22 22:15:01 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-22 22:15:01 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-22 22:15:01 (4182) [INFO] * 2023-03-22 22:15:01 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-22 22:15:01 (4151) [INFO] * 2023-03-22 22:15:23 (4165) [INFO] * 2023-03-22 22:15:23 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-22 22:15:23 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-22 22:15:24 (4182) [INFO] * 2023-03-22 22:15:24 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-22 22:15:24 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-22 22:15:24 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-22 22:15:24 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MU3iGUyO7n/ea_profile.json * 2023-03-22 22:15:24 (1765) [INFO] Backed up EA4 profile to /tmp/MU3iGUyO7n/ea_profile.json * 2023-03-22 22:15:24 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-22 22:15:24 (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 22:15:25 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-23 22:14:44 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-23 22:15:13 (3638) [INFO] Checking if your system is up to date: * 2023-03-23 22:15:13 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-23 22:15:13 (4151) [INFO] * 2023-03-23 22:15:13 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-23 22:15:13 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-23 22:15:13 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-23 22:15:13 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-23 22:15:13 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-23 22:15:13 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-23 22:15:13 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-23 22:15:13 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-23 22:15:13 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-23 22:15:14 (4182) [INFO] * 2023-03-23 22:15:14 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-23 22:15:14 (4151) [INFO] * 2023-03-23 22:15:14 (4165) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 25297. * 2023-03-23 22:15:14 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2023-03-23 22:15:14 (4165) [INFO] The other application is: yum * 2023-03-23 22:15:14 (4165) [INFO] Memory : 54 M RSS (380 MB VSZ) * 2023-03-23 22:15:14 (4165) [INFO] Started: Thu Mar 23 22:15:00 2023 - 00:14 ago * 2023-03-23 22:15:14 (4165) [INFO] State : Running, pid: 25297 * 2023-03-23 22:15:37 (4165) [INFO] * 2023-03-23 22:15:37 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-23 22:15:37 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-23 22:15:37 (4182) [INFO] * 2023-03-23 22:15:37 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-23 22:15:37 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-23 22:15:37 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-23 22:15:37 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g_S8XWFs2u/ea_profile.json * 2023-03-23 22:15:38 (1765) [INFO] Backed up EA4 profile to /tmp/g_S8XWFs2u/ea_profile.json * 2023-03-23 22:15:38 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-23 22:15:38 (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 22:15:38 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-24 22:14:03 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-24 22:14:26 (3638) [INFO] Checking if your system is up to date: * 2023-03-24 22:14:26 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-24 22:14:26 (4151) [INFO] * 2023-03-24 22:14:26 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-24 22:14:26 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-24 22:14:26 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-24 22:14:26 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-24 22:14:26 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-24 22:14:26 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-24 22:14:26 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-24 22:14:26 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-24 22:14:26 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-24 22:14:26 (4182) [INFO] * 2023-03-24 22:14:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-24 22:14:26 (4151) [INFO] * 2023-03-24 22:14:52 (4165) [INFO] * 2023-03-24 22:14:52 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-24 22:14:52 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-24 22:14:52 (4182) [INFO] * 2023-03-24 22:14:52 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-24 22:14:52 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-24 22:14:52 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-24 22:14:52 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q5cQR7kbd4/ea_profile.json * 2023-03-24 22:14:53 (1765) [INFO] Backed up EA4 profile to /tmp/q5cQR7kbd4/ea_profile.json * 2023-03-24 22:14:53 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-24 22:14:53 (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 22:14:53 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-25 22:14:54 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-25 22:15:16 (3638) [INFO] Checking if your system is up to date: * 2023-03-25 22:15:16 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-25 22:15:16 (4151) [INFO] * 2023-03-25 22:15:16 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-25 22:15:16 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-25 22:15:16 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-25 22:15:16 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-25 22:15:16 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-25 22:15:16 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-25 22:15:16 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-25 22:15:17 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-25 22:15:17 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-25 22:15:17 (4182) [INFO] * 2023-03-25 22:15:17 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-25 22:15:17 (4151) [INFO] * 2023-03-25 22:15:39 (4165) [INFO] * 2023-03-25 22:15:39 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-25 22:15:39 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-25 22:15:40 (4182) [INFO] * 2023-03-25 22:15:40 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-25 22:15:40 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-25 22:15:40 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-25 22:15:40 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ymfbQXpoKj/ea_profile.json * 2023-03-25 22:15:40 (1765) [INFO] Backed up EA4 profile to /tmp/ymfbQXpoKj/ea_profile.json * 2023-03-25 22:15:40 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-25 22:15:40 (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 22:15:41 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-26 22:14:50 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-26 22:15:13 (3638) [INFO] Checking if your system is up to date: * 2023-03-26 22:15:13 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-26 22:15:13 (4151) [INFO] * 2023-03-26 22:15:13 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-26 22:15:13 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-26 22:15:13 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-26 22:15:13 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-26 22:15:13 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-26 22:15:13 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-26 22:15:13 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-26 22:15:13 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-26 22:15:13 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-26 22:15:13 (4182) [INFO] * 2023-03-26 22:15:13 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-26 22:15:13 (4151) [INFO] * 2023-03-26 22:15:36 (4165) [INFO] * 2023-03-26 22:15:36 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-26 22:15:36 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-26 22:15:37 (4182) [INFO] * 2023-03-26 22:15:37 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-26 22:15:37 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-26 22:15:37 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-26 22:15:37 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FTkzSy1xOq/ea_profile.json * 2023-03-26 22:15:37 (1765) [INFO] Backed up EA4 profile to /tmp/FTkzSy1xOq/ea_profile.json * 2023-03-26 22:15:37 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-26 22:15:38 (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-26 22:15:38 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-27 22:13:58 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-27 22:14:31 (3638) [INFO] Checking if your system is up to date: * 2023-03-27 22:14:31 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-27 22:14:31 (4151) [INFO] * 2023-03-27 22:14:32 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-27 22:14:32 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-27 22:14:32 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-27 22:14:32 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-27 22:14:32 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-27 22:14:32 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-27 22:14:32 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-27 22:14:33 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-27 22:14:33 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-27 22:14:33 (4182) [INFO] * 2023-03-27 22:14:33 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-27 22:14:33 (4151) [INFO] * 2023-03-27 22:14:56 (4165) [INFO] * 2023-03-27 22:14:56 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-27 22:14:56 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-27 22:14:56 (4182) [INFO] * 2023-03-27 22:14:56 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-27 22:14:56 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-27 22:14:56 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-27 22:14:56 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4y_gQ3bR1B/ea_profile.json * 2023-03-27 22:14:57 (1765) [INFO] Backed up EA4 profile to /tmp/4y_gQ3bR1B/ea_profile.json * 2023-03-27 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-27 22:14:57 (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 22:14:58 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-28 22:13:59 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-28 22:14:25 (3638) [INFO] Checking if your system is up to date: * 2023-03-28 22:14:25 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-28 22:14:25 (4151) [INFO] * 2023-03-28 22:14:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-28 22:14:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-28 22:14:25 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-28 22:14:25 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-28 22:14:25 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-28 22:14:25 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-28 22:14:25 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-28 22:14:26 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-28 22:14:26 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-28 22:14:26 (4182) [INFO] * 2023-03-28 22:14:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-28 22:14:26 (4151) [INFO] * 2023-03-28 22:14:46 (4165) [INFO] * 2023-03-28 22:14:46 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-28 22:14:46 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-28 22:14:46 (4182) [INFO] * 2023-03-28 22:14:46 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-28 22:14:46 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-28 22:14:46 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-28 22:14:46 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i6QCdauuyK/ea_profile.json * 2023-03-28 22:14:47 (1765) [INFO] Backed up EA4 profile to /tmp/i6QCdauuyK/ea_profile.json * 2023-03-28 22:14:47 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-28 22:14:47 (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 22:14:47 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-29 22:16:31 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-29 22:16:54 (3638) [INFO] Checking if your system is up to date: * 2023-03-29 22:16:54 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-29 22:16:54 (4151) [INFO] * 2023-03-29 22:16:54 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-29 22:16:54 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-29 22:16:54 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-29 22:16:54 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-29 22:16:54 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-29 22:16:54 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-29 22:16:54 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-29 22:16:54 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-29 22:16:54 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-29 22:16:54 (4182) [INFO] * 2023-03-29 22:16:54 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-29 22:16:54 (4151) [INFO] * 2023-03-29 22:17:21 (4165) [INFO] * 2023-03-29 22:17:21 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-29 22:17:21 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-29 22:17:22 (4182) [INFO] * 2023-03-29 22:17:22 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-29 22:17:22 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-29 22:17:22 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-29 22:17:22 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RKQuxUREPH/ea_profile.json * 2023-03-29 22:17:22 (1765) [INFO] Backed up EA4 profile to /tmp/RKQuxUREPH/ea_profile.json * 2023-03-29 22:17:22 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-29 22:17:22 (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 22:17:23 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-30 22:14:04 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-30 22:14:26 (3638) [INFO] Checking if your system is up to date: * 2023-03-30 22:14:26 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-30 22:14:26 (4151) [INFO] * 2023-03-30 22:14:27 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-30 22:14:27 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-30 22:14:27 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-30 22:14:27 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-30 22:14:27 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-30 22:14:27 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-30 22:14:27 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-30 22:14:27 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-30 22:14:27 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-30 22:14:27 (4182) [INFO] * 2023-03-30 22:14:27 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-30 22:14:27 (4151) [INFO] * 2023-03-30 22:14:47 (4165) [INFO] * 2023-03-30 22:14:47 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-30 22:14:47 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-30 22:14:47 (4182) [INFO] * 2023-03-30 22:14:47 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-30 22:14:47 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-30 22:14:47 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-30 22:14:47 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J4cyzmFcTt/ea_profile.json * 2023-03-30 22:14:48 (1765) [INFO] Backed up EA4 profile to /tmp/J4cyzmFcTt/ea_profile.json * 2023-03-30 22:14:48 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-30 22:14:48 (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 22:14:49 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-03-31 22:14:39 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-03-31 22:15:03 (3638) [INFO] Checking if your system is up to date: * 2023-03-31 22:15:03 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-03-31 22:15:03 (4151) [INFO] * 2023-03-31 22:15:03 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-03-31 22:15:03 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-03-31 22:15:03 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-03-31 22:15:03 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-03-31 22:15:03 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-03-31 22:15:03 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-03-31 22:15:03 (4165) [INFO] : wp-toolkit-thirdparties * 2023-03-31 22:15:03 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-03-31 22:15:03 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-03-31 22:15:03 (4182) [INFO] * 2023-03-31 22:15:03 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-03-31 22:15:03 (4151) [INFO] * 2023-03-31 22:15:29 (4165) [INFO] * 2023-03-31 22:15:29 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-03-31 22:15:29 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-03-31 22:15:29 (4182) [INFO] * 2023-03-31 22:15:29 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-03-31 22:15:29 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-03-31 22:15:29 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-03-31 22:15:29 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B8HBAUdcHb/ea_profile.json * 2023-03-31 22:15:30 (1765) [INFO] Backed up EA4 profile to /tmp/B8HBAUdcHb/ea_profile.json * 2023-03-31 22:15:30 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-03-31 22:15:30 (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 22:15:30 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-01 22:14:49 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-01 22:15:13 (3638) [INFO] Checking if your system is up to date: * 2023-04-01 22:15:13 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-01 22:15:13 (4151) [INFO] * 2023-04-01 22:15:13 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-01 22:15:13 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-01 22:15:13 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-01 22:15:13 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-01 22:15:13 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-01 22:15:13 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-01 22:15:13 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-01 22:15:13 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-01 22:15:13 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-01 22:15:13 (4182) [INFO] * 2023-04-01 22:15:13 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-01 22:15:13 (4151) [INFO] * 2023-04-01 22:15:36 (4165) [INFO] * 2023-04-01 22:15:36 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-01 22:15:36 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-01 22:15:36 (4182) [INFO] * 2023-04-01 22:15:36 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-01 22:15:36 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-01 22:15:36 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-01 22:15:36 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8Ta4b1YoPj/ea_profile.json * 2023-04-01 22:15:37 (1765) [INFO] Backed up EA4 profile to /tmp/8Ta4b1YoPj/ea_profile.json * 2023-04-01 22:15:37 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-01 22:15:37 (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 22:15:37 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-02 22:14:58 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-02 22:15:24 (3638) [INFO] Checking if your system is up to date: * 2023-04-02 22:15:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-02 22:15:24 (4151) [INFO] * 2023-04-02 22:15:24 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-02 22:15:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-02 22:15:25 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-02 22:15:25 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-02 22:15:25 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-02 22:15:25 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-02 22:15:25 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-02 22:15:25 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-02 22:15:25 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-02 22:15:25 (4182) [INFO] * 2023-04-02 22:15:25 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-02 22:15:25 (4151) [INFO] * 2023-04-02 22:15:51 (4165) [INFO] * 2023-04-02 22:15:51 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-02 22:15:51 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-02 22:15:51 (4182) [INFO] * 2023-04-02 22:15:51 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-02 22:15:51 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-02 22:15:51 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-02 22:15:51 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JF7BOtYmQF/ea_profile.json * 2023-04-02 22:15:52 (1765) [INFO] Backed up EA4 profile to /tmp/JF7BOtYmQF/ea_profile.json * 2023-04-02 22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-02 22:15: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 22:15:52 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-03 22:13:56 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-03 22:14:24 (3638) [INFO] Checking if your system is up to date: * 2023-04-03 22:14:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-03 22:14:24 (4151) [INFO] * 2023-04-03 22:14:24 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-03 22:14:24 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-03 22:14:24 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-03 22:14:24 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-03 22:14:24 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-03 22:14:24 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-03 22:14:24 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-03 22:14:24 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-03 22:14:24 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-03 22:14:24 (4182) [INFO] * 2023-04-03 22:14:24 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-03 22:14:24 (4151) [INFO] * 2023-04-03 22:14:45 (4165) [INFO] * 2023-04-03 22:14:45 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-03 22:14:45 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-03 22:14:45 (4182) [INFO] * 2023-04-03 22:14:45 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-03 22:14:45 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-03 22:14:45 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-03 22:14:45 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qNz20Yf6SV/ea_profile.json * 2023-04-03 22:14:46 (1765) [INFO] Backed up EA4 profile to /tmp/qNz20Yf6SV/ea_profile.json * 2023-04-03 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-03 22:14: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-03 22:14:47 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-04 22:14:15 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-04 22:14:42 (3638) [INFO] Checking if your system is up to date: * 2023-04-04 22:14:42 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-04 22:14:42 (4151) [INFO] * 2023-04-04 22:14:42 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-04 22:14:43 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-04 22:14:43 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-04 22:14:43 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-04 22:14:43 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-04 22:14:43 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-04 22:14:43 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-04 22:14:43 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-04 22:14:43 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-04 22:14:43 (4182) [INFO] * 2023-04-04 22:14:43 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-04 22:14:43 (4151) [INFO] * 2023-04-04 22:15:05 (4165) [INFO] * 2023-04-04 22:15:05 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-04 22:15:05 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-04 22:15:05 (4182) [INFO] * 2023-04-04 22:15:05 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-04 22:15:05 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-04 22:15:05 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-04 22:15:05 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/928cXkUXlm/ea_profile.json * 2023-04-04 22:15:06 (1765) [INFO] Backed up EA4 profile to /tmp/928cXkUXlm/ea_profile.json * 2023-04-04 22:15:06 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-04 22:15:06 (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 22:15:06 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-05 22:14:12 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-05 22:14:36 (3638) [INFO] Checking if your system is up to date: * 2023-04-05 22:14:36 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-05 22:14:36 (4151) [INFO] * 2023-04-05 22:14:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-05 22:14:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-05 22:14:37 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-05 22:14:37 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-05 22:14:37 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-05 22:14:37 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-05 22:14:37 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-05 22:14:37 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-05 22:14:37 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-05 22:14:37 (4182) [INFO] * 2023-04-05 22:14:37 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-05 22:14:37 (4151) [INFO] * 2023-04-05 22:14:57 (4165) [INFO] * 2023-04-05 22:14:57 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-05 22:14:57 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-05 22:14:58 (4182) [INFO] * 2023-04-05 22:14:58 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-05 22:14:58 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-05 22:14:58 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-05 22:14:58 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YElkrgKIJt/ea_profile.json * 2023-04-05 22:14:58 (1765) [INFO] Backed up EA4 profile to /tmp/YElkrgKIJt/ea_profile.json * 2023-04-05 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-05 22:14: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-04-05 22:14:59 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-06 22:15:13 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-06 22:15:43 (3638) [INFO] Checking if your system is up to date: * 2023-04-06 22:15:43 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-06 22:15:43 (4151) [INFO] * 2023-04-06 22:15:43 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-06 22:15:43 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-06 22:15:43 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-06 22:15:43 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-06 22:15:43 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-06 22:15:43 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-06 22:15:43 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-06 22:15:43 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-06 22:15:43 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-06 22:15:43 (4182) [INFO] * 2023-04-06 22:15:43 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-06 22:15:43 (4151) [INFO] * 2023-04-06 22:16:05 (4165) [INFO] * 2023-04-06 22:16:05 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-06 22:16:05 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-06 22:16:05 (4182) [INFO] * 2023-04-06 22:16:05 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-06 22:16:05 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-06 22:16:05 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-06 22:16:05 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EpIg_d5Raa/ea_profile.json * 2023-04-06 22:16:06 (1765) [INFO] Backed up EA4 profile to /tmp/EpIg_d5Raa/ea_profile.json * 2023-04-06 22:16:06 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-06 22:16:06 (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 22:16:06 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-07 22:13:59 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-07 22:14:25 (3638) [INFO] Checking if your system is up to date: * 2023-04-07 22:14:25 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-07 22:14:25 (4151) [INFO] * 2023-04-07 22:14:26 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-07 22:14:26 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-07 22:14:26 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-07 22:14:26 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-07 22:14:26 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-07 22:14:26 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-07 22:14:26 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-07 22:14:26 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-07 22:14:26 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-07 22:14:26 (4182) [INFO] * 2023-04-07 22:14:26 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-07 22:14:26 (4151) [INFO] * 2023-04-07 22:14:47 (4165) [INFO] * 2023-04-07 22:14:47 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-07 22:14:47 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-07 22:14:47 (4182) [INFO] * 2023-04-07 22:14:47 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-07 22:14:47 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-07 22:14:47 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-07 22:14:47 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VjfmO69RII/ea_profile.json * 2023-04-07 22:14:48 (1765) [INFO] Backed up EA4 profile to /tmp/VjfmO69RII/ea_profile.json * 2023-04-07 22:14:48 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-07 22:14:48 (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 22:14:48 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-08 22:15:04 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-08 22:15:27 (3638) [INFO] Checking if your system is up to date: * 2023-04-08 22:15:27 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-08 22:15:27 (4151) [INFO] * 2023-04-08 22:15:28 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-08 22:15:28 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-08 22:15:28 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-08 22:15:28 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-08 22:15:28 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-08 22:15:28 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-08 22:15:28 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-08 22:15:28 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-08 22:15:28 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-08 22:15:28 (4182) [INFO] * 2023-04-08 22:15:28 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-08 22:15:28 (4151) [INFO] * 2023-04-08 22:15:51 (4165) [INFO] * 2023-04-08 22:15:51 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-08 22:15:51 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-08 22:15:51 (4182) [INFO] * 2023-04-08 22:15:51 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-08 22:15:51 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-08 22:15:51 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-08 22:15:51 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6kLQ29jm82/ea_profile.json * 2023-04-08 22:15:52 (1765) [INFO] Backed up EA4 profile to /tmp/6kLQ29jm82/ea_profile.json * 2023-04-08 22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-08 22:15: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-08 22:15:52 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-09 22:14:57 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-09 22:15:21 (3638) [INFO] Checking if your system is up to date: * 2023-04-09 22:15:21 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-09 22:15:21 (4151) [INFO] * 2023-04-09 22:15:22 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-09 22:15:22 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-09 22:15:22 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-09 22:15:22 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-09 22:15:22 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-09 22:15:22 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-09 22:15:22 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-09 22:15:22 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-09 22:15:22 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-09 22:15:22 (4182) [INFO] * 2023-04-09 22:15:22 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-09 22:15:22 (4151) [INFO] * 2023-04-09 22:15:44 (4165) [INFO] * 2023-04-09 22:15:44 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-09 22:15:44 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-09 22:15:44 (4182) [INFO] * 2023-04-09 22:15:44 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-09 22:15:44 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-09 22:15:44 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-09 22:15:44 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WFfE0Y_Dqv/ea_profile.json * 2023-04-09 22:15:45 (1765) [INFO] Backed up EA4 profile to /tmp/WFfE0Y_Dqv/ea_profile.json * 2023-04-09 22:15:45 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-09 22:15:45 (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 22:15:45 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-10 22:14:00 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-10 22:14:24 (3638) [INFO] Checking if your system is up to date: * 2023-04-10 22:14:24 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-10 22:14:24 (4151) [INFO] * 2023-04-10 22:14:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-10 22:14:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-10 22:14:25 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-10 22:14:25 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-10 22:14:25 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-10 22:14:25 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-10 22:14:25 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-10 22:14:25 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-10 22:14:25 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-10 22:14:25 (4182) [INFO] * 2023-04-10 22:14:25 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-10 22:14:25 (4151) [INFO] * 2023-04-10 22:14:45 (4165) [INFO] * 2023-04-10 22:14:45 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-10 22:14:45 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-10 22:14:46 (4182) [INFO] * 2023-04-10 22:14:46 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-10 22:14:46 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-10 22:14:46 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-10 22:14:46 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0JG9l6aOR9/ea_profile.json * 2023-04-10 22:14:46 (1765) [INFO] Backed up EA4 profile to /tmp/0JG9l6aOR9/ea_profile.json * 2023-04-10 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-10 22:14:47 (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 22:14:47 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-11 22:14:08 (2820) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-11 22:14:33 (3638) [INFO] Checking if your system is up to date: * 2023-04-11 22:14:33 (4150) [INFO] Running: /usr/bin/yum clean all * 2023-04-11 22:14:33 (4151) [INFO] * 2023-04-11 22:14:35 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-11 22:14:35 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-11 22:14:35 (4165) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-11 22:14:35 (4165) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-11 22:14:35 (4165) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-11 22:14:35 (4165) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-11 22:14:35 (4165) [INFO] : wp-toolkit-thirdparties * 2023-04-11 22:14:35 (4165) [INFO] Cleaning up list of fastest mirrors * 2023-04-11 22:14:35 (4165) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-11 22:14:35 (4182) [INFO] * 2023-04-11 22:14:35 (4150) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-11 22:14:35 (4151) [INFO] * 2023-04-11 22:14:56 (4165) [INFO] * 2023-04-11 22:14:56 (4165) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-11 22:14:56 (4165) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-11 22:14:56 (4182) [INFO] * 2023-04-11 22:14:56 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-11 22:14:56 (2820) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-11 22:14:56 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-11 22:14:56 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MAn8IktmSe/ea_profile.json * 2023-04-11 22:14:57 (1765) [INFO] Backed up EA4 profile to /tmp/MAn8IktmSe/ea_profile.json * 2023-04-11 22:14: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-11 22:14:57 (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 22:14:57 (759) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-12 22:14:09 (372) [INFO] Self-update of script version 6 requested. * 2023-04-12 22:14:09 (377) [INFO] Newer version of script found. Downloading. * 2023-04-12 22:14:09 (386) [INFO] Script update to version 7 successful. * 2023-04-12 22:14:10 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-12 22:14:33 (3686) [INFO] Checking if your system is up to date: * 2023-04-12 22:14:33 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-12 22:14:33 (4199) [INFO] * 2023-04-12 22:14:33 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-12 22:14:33 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-12 22:14:33 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-12 22:14:33 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-12 22:14:33 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-12 22:14:33 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-12 22:14:33 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-12 22:14:33 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-12 22:14:33 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-12 22:14:33 (4230) [INFO] * 2023-04-12 22:14:33 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-12 22:14:33 (4199) [INFO] * 2023-04-12 22:14:53 (4213) [INFO] * 2023-04-12 22:14:53 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-12 22:14:53 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-12 22:14:53 (4230) [INFO] * 2023-04-12 22:14:53 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-12 22:14:53 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-12 22:14:53 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-12 22:14:53 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CYp9q2eyZJ/ea_profile.json * 2023-04-12 22:14:54 (1805) [INFO] Backed up EA4 profile to /tmp/CYp9q2eyZJ/ea_profile.json * 2023-04-12 22:14:54 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-12 22:14: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-12 22:14:54 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-13 22:15:44 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-13 22:16:06 (3686) [INFO] Checking if your system is up to date: * 2023-04-13 22:16:06 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-13 22:16:06 (4199) [INFO] * 2023-04-13 22:16:06 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-13 22:16:06 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-13 22:16:06 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-13 22:16:06 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-13 22:16:06 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-13 22:16:06 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-13 22:16:06 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-13 22:16:06 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-13 22:16:06 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-13 22:16:06 (4230) [INFO] * 2023-04-13 22:16:06 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-13 22:16:06 (4199) [INFO] * 2023-04-13 22:16:27 (4213) [INFO] * 2023-04-13 22:16:27 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-13 22:16:27 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-13 22:16:27 (4230) [INFO] * 2023-04-13 22:16:27 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-13 22:16:27 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-13 22:16:27 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-13 22:16:27 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i6LaOkbg6b/ea_profile.json * 2023-04-13 22:16:28 (1805) [INFO] Backed up EA4 profile to /tmp/i6LaOkbg6b/ea_profile.json * 2023-04-13 22:16:28 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-13 22:16:28 (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 22:16:28 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-14 22:14:01 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-14 22:14:28 (3686) [INFO] Checking if your system is up to date: * 2023-04-14 22:14:28 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-14 22:14:28 (4199) [INFO] * 2023-04-14 22:14:28 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-14 22:14:28 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-14 22:14:28 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-14 22:14:28 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-14 22:14:28 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-14 22:14:28 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-14 22:14:28 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-14 22:14:29 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-14 22:14:29 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-14 22:14:29 (4230) [INFO] * 2023-04-14 22:14:29 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-14 22:14:29 (4199) [INFO] * 2023-04-14 22:14:50 (4213) [INFO] * 2023-04-14 22:14:50 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-14 22:14:50 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-14 22:14:50 (4230) [INFO] * 2023-04-14 22:14:50 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-14 22:14:50 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-14 22:14:50 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-14 22:14:50 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/f7g445hGr7/ea_profile.json * 2023-04-14 22:14:51 (1805) [INFO] Backed up EA4 profile to /tmp/f7g445hGr7/ea_profile.json * 2023-04-14 22:14:51 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-14 22:14:51 (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 22:14:51 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-15 22:14:54 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-15 22:15:20 (3686) [INFO] Checking if your system is up to date: * 2023-04-15 22:15:20 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-15 22:15:20 (4199) [INFO] * 2023-04-15 22:15:20 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-15 22:15:20 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-15 22:15:20 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-15 22:15:20 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-15 22:15:20 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-15 22:15:20 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-15 22:15:20 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-15 22:15:20 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-15 22:15:20 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-15 22:15:20 (4230) [INFO] * 2023-04-15 22:15:20 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-15 22:15:20 (4199) [INFO] * 2023-04-15 22:15:41 (4213) [INFO] * 2023-04-15 22:15:41 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-15 22:15:41 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-15 22:15:42 (4230) [INFO] * 2023-04-15 22:15:42 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-15 22:15:42 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-15 22:15:42 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-15 22:15:42 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j4a6LtNn2V/ea_profile.json * 2023-04-15 22:15:42 (1805) [INFO] Backed up EA4 profile to /tmp/j4a6LtNn2V/ea_profile.json * 2023-04-15 22:15:42 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-15 22:15:42 (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 22:15:43 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-16 22:14:59 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-16 22:15:24 (3686) [INFO] Checking if your system is up to date: * 2023-04-16 22:15:24 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-16 22:15:24 (4199) [INFO] * 2023-04-16 22:15:24 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-16 22:15:24 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-16 22:15:24 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-16 22:15:24 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-16 22:15:24 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-16 22:15:24 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-16 22:15:24 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-16 22:15:24 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-16 22:15:24 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-16 22:15:24 (4230) [INFO] * 2023-04-16 22:15:24 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-16 22:15:24 (4199) [INFO] * 2023-04-16 22:15:48 (4213) [INFO] * 2023-04-16 22:15:48 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-16 22:15:48 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-16 22:15:48 (4230) [INFO] * 2023-04-16 22:15:48 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-16 22:15:48 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-16 22:15:48 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-16 22:15:48 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m0gvAhthz7/ea_profile.json * 2023-04-16 22:15:49 (1805) [INFO] Backed up EA4 profile to /tmp/m0gvAhthz7/ea_profile.json * 2023-04-16 22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-16 22:15: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-16 22:15:49 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-17 22:15:42 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-17 22:16:06 (3686) [INFO] Checking if your system is up to date: * 2023-04-17 22:16:06 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-17 22:16:06 (4199) [INFO] * 2023-04-17 22:16:06 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-17 22:16:07 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-17 22:16:07 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-17 22:16:07 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-17 22:16:07 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-17 22:16:07 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-17 22:16:07 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-17 22:16:07 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-17 22:16:07 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-17 22:16:07 (4230) [INFO] * 2023-04-17 22:16:07 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-17 22:16:07 (4199) [INFO] * 2023-04-17 22:16:28 (4213) [INFO] * 2023-04-17 22:16:28 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-17 22:16:28 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-17 22:16:28 (4230) [INFO] * 2023-04-17 22:16:28 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-17 22:16:28 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-17 22:16:28 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-17 22:16:28 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AeprY7cjfh/ea_profile.json * 2023-04-17 22:16:29 (1805) [INFO] Backed up EA4 profile to /tmp/AeprY7cjfh/ea_profile.json * 2023-04-17 22:16:29 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-17 22:16:29 (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 22:16:29 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-18 22:14:14 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-18 22:14:37 (3686) [INFO] Checking if your system is up to date: * 2023-04-18 22:14:37 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-18 22:14:37 (4199) [INFO] * 2023-04-18 22:14:37 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-18 22:14:37 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-18 22:14:37 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-18 22:14:37 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-18 22:14:37 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-18 22:14:37 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-18 22:14:37 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-18 22:14:37 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-18 22:14:37 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-18 22:14:37 (4230) [INFO] * 2023-04-18 22:14:37 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-18 22:14:37 (4199) [INFO] * 2023-04-18 22:15:00 (4213) [INFO] * 2023-04-18 22:15:00 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-18 22:15:00 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-18 22:15:00 (4230) [INFO] * 2023-04-18 22:15:00 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-18 22:15:00 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-18 22:15:00 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-18 22:15:00 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LuAmEJ5UE6/ea_profile.json * 2023-04-18 22:15:01 (1805) [INFO] Backed up EA4 profile to /tmp/LuAmEJ5UE6/ea_profile.json * 2023-04-18 22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-18 22:15: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-18 22:15:02 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-19 22:16:28 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-19 22:16:35 (3686) [INFO] Checking if your system is up to date: * 2023-04-19 22:16:35 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-19 22:16:35 (4199) [INFO] * 2023-04-19 22:16:36 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-19 22:16:36 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-19 22:16:36 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-19 22:16:36 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-19 22:16:36 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-19 22:16:36 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-19 22:16:36 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-19 22:16:36 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-19 22:16:36 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-19 22:16:36 (4230) [INFO] * 2023-04-19 22:16:36 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-19 22:16:36 (4199) [INFO] * 2023-04-19 22:16:57 (4213) [INFO] * 2023-04-19 22:16:57 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-19 22:16:57 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-19 22:16:57 (4230) [INFO] * 2023-04-19 22:16:57 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-19 22:16:57 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-19 22:16:57 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-19 22:16:57 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E5r1TSF9aC/ea_profile.json * 2023-04-19 22:16:58 (1805) [INFO] Backed up EA4 profile to /tmp/E5r1TSF9aC/ea_profile.json * 2023-04-19 22:16:58 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-19 22:16:58 (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 22:16:58 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-20 22:15:21 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-20 22:15:49 (3686) [INFO] Checking if your system is up to date: * 2023-04-20 22:15:49 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-20 22:15:49 (4199) [INFO] * 2023-04-20 22:15:49 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-20 22:15:49 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-20 22:15:49 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-20 22:15:49 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-20 22:15:49 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-20 22:15:49 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-20 22:15:49 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-20 22:15:49 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-20 22:15:49 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-20 22:15:49 (4230) [INFO] * 2023-04-20 22:15:49 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-20 22:15:49 (4199) [INFO] * 2023-04-20 22:16:14 (4213) [INFO] * 2023-04-20 22:16:14 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-20 22:16:14 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-20 22:16:14 (4230) [INFO] * 2023-04-20 22:16:14 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-20 22:16:14 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-20 22:16:14 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-20 22:16:14 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bwPJ56U9L1/ea_profile.json * 2023-04-20 22:16:14 (1805) [INFO] Backed up EA4 profile to /tmp/bwPJ56U9L1/ea_profile.json * 2023-04-20 22:16:14 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-20 22:16:15 (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 22:16:15 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-21 22:14:01 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-21 22:14:24 (3686) [INFO] Checking if your system is up to date: * 2023-04-21 22:14:24 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-21 22:14:24 (4199) [INFO] * 2023-04-21 22:14:25 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-21 22:14:25 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-21 22:14:25 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-21 22:14:25 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-21 22:14:25 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-21 22:14:25 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-21 22:14:25 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-21 22:14:25 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-21 22:14:25 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-21 22:14:25 (4230) [INFO] * 2023-04-21 22:14:25 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-21 22:14:25 (4199) [INFO] * 2023-04-21 22:14:46 (4213) [INFO] * 2023-04-21 22:14:46 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-21 22:14:46 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-21 22:14:46 (4230) [INFO] * 2023-04-21 22:14:46 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-21 22:14:46 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-21 22:14:46 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-21 22:14:46 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cgY9W4NiQJ/ea_profile.json * 2023-04-21 22:14:47 (1805) [INFO] Backed up EA4 profile to /tmp/cgY9W4NiQJ/ea_profile.json * 2023-04-21 22:14:47 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-21 22:14:47 (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 22:14:47 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-22 22:14:57 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-22 22:15:22 (3686) [INFO] Checking if your system is up to date: * 2023-04-22 22:15:22 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-22 22:15:22 (4199) [INFO] * 2023-04-22 22:15:23 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-22 22:15:23 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-22 22:15:23 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-22 22:15:23 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-22 22:15:23 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-22 22:15:23 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-22 22:15:23 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-22 22:15:23 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-22 22:15:23 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-22 22:15:23 (4230) [INFO] * 2023-04-22 22:15:23 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-22 22:15:23 (4199) [INFO] * 2023-04-22 22:15:45 (4213) [INFO] * 2023-04-22 22:15:45 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-22 22:15:45 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-22 22:15:45 (4230) [INFO] * 2023-04-22 22:15:45 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-22 22:15:45 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-22 22:15:46 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-22 22:15:46 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yp1SvuRnr4/ea_profile.json * 2023-04-22 22:15:47 (1805) [INFO] Backed up EA4 profile to /tmp/yp1SvuRnr4/ea_profile.json * 2023-04-22 22:15:47 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-22 22:15:47 (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 22:15:47 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-23 22:14:58 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-23 22:15:25 (3686) [INFO] Checking if your system is up to date: * 2023-04-23 22:15:25 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-23 22:15:25 (4199) [INFO] * 2023-04-23 22:15:25 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-23 22:15:25 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-23 22:15:25 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-23 22:15:25 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-23 22:15:25 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-23 22:15:25 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-23 22:15:25 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-23 22:15:25 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-23 22:15:25 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-23 22:15:25 (4230) [INFO] * 2023-04-23 22:15:25 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-23 22:15:25 (4199) [INFO] * 2023-04-23 22:15:47 (4213) [INFO] * 2023-04-23 22:15:47 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-23 22:15:47 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-23 22:15:47 (4230) [INFO] * 2023-04-23 22:15:47 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-23 22:15:47 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-23 22:15:47 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-23 22:15:47 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7t1BFvqvlq/ea_profile.json * 2023-04-23 22:15:48 (1805) [INFO] Backed up EA4 profile to /tmp/7t1BFvqvlq/ea_profile.json * 2023-04-23 22:15:48 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-23 22:15:48 (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 22:15:48 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-24 22:14:12 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-24 22:14:36 (3686) [INFO] Checking if your system is up to date: * 2023-04-24 22:14:36 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-24 22:14:36 (4199) [INFO] * 2023-04-24 22:14:36 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-24 22:14:36 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-24 22:14:36 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-24 22:14:36 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-24 22:14:36 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-24 22:14:36 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-24 22:14:36 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-24 22:14:36 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-24 22:14:36 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-24 22:14:36 (4230) [INFO] * 2023-04-24 22:14:36 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-24 22:14:36 (4199) [INFO] * 2023-04-24 22:14:59 (4213) [INFO] * 2023-04-24 22:14:59 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-24 22:14:59 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-24 22:14:59 (4230) [INFO] * 2023-04-24 22:14:59 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-24 22:14:59 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-24 22:14:59 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-24 22:14:59 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vrJmiVecc1/ea_profile.json * 2023-04-24 22:15:00 (1805) [INFO] Backed up EA4 profile to /tmp/vrJmiVecc1/ea_profile.json * 2023-04-24 22:15: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-24 22:15: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-24 22:15:01 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-25 22:14:01 (2856) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-25 22:14:27 (3686) [INFO] Checking if your system is up to date: * 2023-04-25 22:14:27 (4198) [INFO] Running: /usr/bin/yum clean all * 2023-04-25 22:14:27 (4199) [INFO] * 2023-04-25 22:14:27 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-25 22:14:27 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-25 22:14:27 (4213) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-25 22:14:27 (4213) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-25 22:14:27 (4213) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-25 22:14:27 (4213) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-25 22:14:27 (4213) [INFO] : wp-toolkit-thirdparties * 2023-04-25 22:14:27 (4213) [INFO] Cleaning up list of fastest mirrors * 2023-04-25 22:14:27 (4213) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-25 22:14:27 (4230) [INFO] * 2023-04-25 22:14:27 (4198) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-25 22:14:27 (4199) [INFO] * 2023-04-25 22:14:49 (4213) [INFO] * 2023-04-25 22:14:49 (4213) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-25 22:14:49 (4213) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-25 22:14:50 (4230) [INFO] * 2023-04-25 22:14:50 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-25 22:14:50 (2856) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-25 22:14:50 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-25 22:14:50 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IVN67vxzmE/ea_profile.json * 2023-04-25 22:14:50 (1805) [INFO] Backed up EA4 profile to /tmp/IVN67vxzmE/ea_profile.json * 2023-04-25 22:14:50 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2023-04-25 22:14:51 (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 22:14:51 (797) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-26 22:15:00 (410) [INFO] Self-update of script version 7 requested. * 2023-04-26 22:15:01 (415) [INFO] Newer version of script found. Downloading. * 2023-04-26 22:15:01 (424) [INFO] Script update to version 8 successful. * 2023-04-26 22:15:03 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-26 22:15:03 (1573) [INFO] Checking if your system is up to date: * 2023-04-26 22:15:03 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-26 22:15:03 (3854) [INFO] * 2023-04-26 22:15:03 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-26 22:15:03 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-26 22:15:03 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-26 22:15:03 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-26 22:15:03 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-26 22:15:03 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-26 22:15:03 (3867) [INFO] : wp-toolkit-thirdparties * 2023-04-26 22:15:03 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-04-26 22:15:03 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-26 22:15:03 (3884) [INFO] * 2023-04-26 22:15:03 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-26 22:15:03 (3854) [INFO] * 2023-04-26 22:15:26 (3867) [INFO] * 2023-04-26 22:15:26 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-26 22:15:26 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-26 22:15:26 (3884) [INFO] * 2023-04-26 22:15:26 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-26 22:15:26 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-26 22:15:47 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-26 22:15:47 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/23h80847oV/ea_profile.json * 2023-04-26 22:15:48 (2038) [INFO] Backed up EA4 profile to /tmp/23h80847oV/ea_profile.json * 2023-04-26 22:15:48 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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 22:15:48 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-27 22:13:57 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-27 22:13:57 (1573) [INFO] Checking if your system is up to date: * 2023-04-27 22:13:57 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-27 22:13:57 (3854) [INFO] * 2023-04-27 22:13:57 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-27 22:13:57 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-27 22:13:57 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-27 22:13:57 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-27 22:13:57 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-27 22:13:57 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-27 22:13:57 (3867) [INFO] : wp-toolkit-thirdparties * 2023-04-27 22:13:57 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-04-27 22:13:57 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-27 22:13:57 (3884) [INFO] * 2023-04-27 22:13:57 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-27 22:13:57 (3854) [INFO] * 2023-04-27 22:14:18 (3867) [INFO] * 2023-04-27 22:14:18 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-27 22:14:18 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-27 22:14:18 (3884) [INFO] * 2023-04-27 22:14:18 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-27 22:14:18 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-27 22:14:41 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-27 22:14:41 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DLMDWbKkSu/ea_profile.json * 2023-04-27 22:14:42 (2038) [INFO] Backed up EA4 profile to /tmp/DLMDWbKkSu/ea_profile.json * 2023-04-27 22:14:42 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-27 22:14:42 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-28 22:13:58 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-28 22:13:58 (1573) [INFO] Checking if your system is up to date: * 2023-04-28 22:13:58 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-28 22:13:58 (3854) [INFO] * 2023-04-28 22:13:58 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-28 22:13:58 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-28 22:13:58 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-28 22:13:58 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-28 22:13:58 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-28 22:13:58 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-28 22:13:58 (3867) [INFO] : wp-toolkit-thirdparties * 2023-04-28 22:13:58 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-04-28 22:13:58 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-28 22:13:58 (3884) [INFO] * 2023-04-28 22:13:58 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-28 22:13:58 (3854) [INFO] * 2023-04-28 22:14:20 (3867) [INFO] * 2023-04-28 22:14:20 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-28 22:14:20 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-28 22:14:20 (3884) [INFO] * 2023-04-28 22:14:20 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-28 22:14:20 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-28 22:14:41 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-28 22:14:41 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vzT5yjU9Rx/ea_profile.json * 2023-04-28 22:14:42 (2038) [INFO] Backed up EA4 profile to /tmp/vzT5yjU9Rx/ea_profile.json * 2023-04-28 22:14:42 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-28 22:14:42 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-29 22:14:57 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-29 22:14:57 (1573) [INFO] Checking if your system is up to date: * 2023-04-29 22:14:57 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-29 22:14:57 (3854) [INFO] * 2023-04-29 22:14:57 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-29 22:14:57 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-29 22:14:57 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-29 22:14:57 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-29 22:14:57 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-29 22:14:57 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-29 22:14:57 (3867) [INFO] : wp-toolkit-thirdparties * 2023-04-29 22:14:57 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-04-29 22:14:57 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-29 22:14:57 (3884) [INFO] * 2023-04-29 22:14:57 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-29 22:14:57 (3854) [INFO] * 2023-04-29 22:15:17 (3867) [INFO] * 2023-04-29 22:15:17 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-29 22:15:17 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-29 22:15:17 (3884) [INFO] * 2023-04-29 22:15:17 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-29 22:15:17 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-29 22:15:41 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-29 22:15:41 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LDATju99Ae/ea_profile.json * 2023-04-29 22:15:42 (2038) [INFO] Backed up EA4 profile to /tmp/LDATju99Ae/ea_profile.json * 2023-04-29 22:15:42 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-29 22:15:42 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-04-30 22:14:52 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-04-30 22:14:52 (1573) [INFO] Checking if your system is up to date: * 2023-04-30 22:14:52 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-04-30 22:14:52 (3854) [INFO] * 2023-04-30 22:14:52 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-04-30 22:14:52 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-04-30 22:14:52 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-04-30 22:14:52 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-04-30 22:14:52 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-04-30 22:14:52 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-04-30 22:14:52 (3867) [INFO] : wp-toolkit-thirdparties * 2023-04-30 22:14:52 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-04-30 22:14:52 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-04-30 22:14:52 (3884) [INFO] * 2023-04-30 22:14:52 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-04-30 22:14:52 (3854) [INFO] * 2023-04-30 22:15:17 (3867) [INFO] * 2023-04-30 22:15:17 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-04-30 22:15:17 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-04-30 22:15:17 (3884) [INFO] * 2023-04-30 22:15:17 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-04-30 22:15:17 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-04-30 22:15:40 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-04-30 22:15:40 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/a7UuDKBHml/ea_profile.json * 2023-04-30 22:15:41 (2038) [INFO] Backed up EA4 profile to /tmp/a7UuDKBHml/ea_profile.json * 2023-04-30 22:15:41 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-30 22:15:41 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-01 22:17:59 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-01 22:17:59 (1573) [INFO] Checking if your system is up to date: * 2023-05-01 22:17:59 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-01 22:17:59 (3854) [INFO] * 2023-05-01 22:17:59 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-01 22:17:59 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-01 22:17:59 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-01 22:17:59 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-01 22:17:59 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-01 22:17:59 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-01 22:17:59 (3867) [INFO] : wp-toolkit-thirdparties * 2023-05-01 22:17:59 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-05-01 22:18:00 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-01 22:18:00 (3884) [INFO] * 2023-05-01 22:18:00 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-01 22:18:00 (3854) [INFO] * 2023-05-01 22:18:26 (3867) [INFO] * 2023-05-01 22:18:26 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-01 22:18:26 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-01 22:18:26 (3884) [INFO] * 2023-05-01 22:18:26 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-01 22:18:26 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-01 22:18:50 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-01 22:18:50 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V2BjYU6B83/ea_profile.json * 2023-05-01 22:18:51 (2038) [INFO] Backed up EA4 profile to /tmp/V2BjYU6B83/ea_profile.json * 2023-05-01 22:18:52 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-01 22:18:52 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-02 22:14:00 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-02 22:14:00 (1573) [INFO] Checking if your system is up to date: * 2023-05-02 22:14:00 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-02 22:14:00 (3854) [INFO] * 2023-05-02 22:14:00 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-02 22:14:00 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-02 22:14:00 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-02 22:14:00 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-02 22:14:00 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-02 22:14:00 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-02 22:14:00 (3867) [INFO] : wp-toolkit-thirdparties * 2023-05-02 22:14:00 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-05-02 22:14:00 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-02 22:14:00 (3884) [INFO] * 2023-05-02 22:14:00 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-02 22:14:00 (3854) [INFO] * 2023-05-02 22:14:21 (3867) [INFO] * 2023-05-02 22:14:21 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-02 22:14:21 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-02 22:14:21 (3884) [INFO] * 2023-05-02 22:14:21 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-02 22:14:21 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-02 22:14:43 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-02 22:14:43 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fAJyHFRsrs/ea_profile.json * 2023-05-02 22:14:43 (2038) [INFO] Backed up EA4 profile to /tmp/fAJyHFRsrs/ea_profile.json * 2023-05-02 22:14:44 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-02 22:14:44 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-03 22:14:10 (144) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-03 22:14:10 (1573) [INFO] Checking if your system is up to date: * 2023-05-03 22:14:10 (3853) [INFO] Running: /usr/bin/yum clean all * 2023-05-03 22:14:10 (3854) [INFO] * 2023-05-03 22:14:10 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-03 22:14:10 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-03 22:14:10 (3867) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-03 22:14:10 (3867) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-03 22:14:10 (3867) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-03 22:14:10 (3867) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-03 22:14:10 (3867) [INFO] : wp-toolkit-thirdparties * 2023-05-03 22:14:11 (3867) [INFO] Cleaning up list of fastest mirrors * 2023-05-03 22:14:11 (3867) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-03 22:14:11 (3884) [INFO] * 2023-05-03 22:14:11 (3853) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-03 22:14:11 (3854) [INFO] * 2023-05-03 22:14:33 (3867) [INFO] * 2023-05-03 22:14:33 (3867) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-03 22:14:33 (3867) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-03 22:14:33 (3884) [INFO] * 2023-05-03 22:14:33 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-03 22:14:33 (144) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-03 22:14:59 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-03 22:14:59 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vX75W3r1Eh/ea_profile.json * 2023-05-03 22:14:59 (2038) [INFO] Backed up EA4 profile to /tmp/vX75W3r1Eh/ea_profile.json * 2023-05-03 22:15:00 (144) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-03 22:15:00 (244) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-04 22:15:21 (145) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-04 22:15:21 (1625) [INFO] Checking if your system is up to date: * 2023-05-04 22:15:21 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-04 22:15:21 (3906) [INFO] * 2023-05-04 22:15:21 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-04 22:15:21 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-04 22:15:21 (3919) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-04 22:15:21 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-04 22:15:21 (3919) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-04 22:15:21 (3919) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-04 22:15:21 (3919) [INFO] : wp-toolkit-thirdparties * 2023-05-04 22:15:21 (3919) [INFO] Cleaning up list of fastest mirrors * 2023-05-04 22:15:21 (3919) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-04 22:15:21 (3936) [INFO] * 2023-05-04 22:15:21 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-04 22:15:21 (3906) [INFO] * 2023-05-04 22:15:28 (3919) [INFO] https://mirrors.ukfast.co.uk/sites/dl.fedoraproject.org/pub/epel/7/x86_64/repodata/345a68da697a2891749407cbc2331ffc6a0756c6100fecbfcb5f183fa9c585f3-updateinfo.xml.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-04 22:15:28 (3919) [INFO] Trying other mirror. * 2023-05-04 22:15:28 (3919) [INFO] To address this issue please refer to the below wiki article * 2023-05-04 22:15:28 (3919) [INFO] * 2023-05-04 22:15:28 (3919) [INFO] https://wiki.centos.org/yum-errors * 2023-05-04 22:15:28 (3919) [INFO] * 2023-05-04 22:15:28 (3919) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-05-04 22:15:28 (3919) [INFO] * 2023-05-04 22:15:46 (3919) [INFO] * 2023-05-04 22:15:46 (3919) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-04 22:15:46 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-04 22:15:46 (3936) [INFO] * 2023-05-04 22:15:46 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-04 22:15:46 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-04 22:16:13 (1491) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-04 22:16:13 (1492) [ERROR] https://mirrors.ukfast.co.uk/sites/dl.fedoraproject.org/pub/epel/7/x86_64/repodata/8a75e320f3b1b1683d14188a08289c242a0585edf0d39cd759272bf97fc20bb1-prestodelta.xml.gz: [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/. * 2023-05-04 22:16:13 (145) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-04 22:16:13 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-04 22:16:13 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RJTvClDRL6/ea_profile.json * 2023-05-04 22:16:14 (2090) [INFO] Backed up EA4 profile to /tmp/RJTvClDRL6/ea_profile.json * 2023-05-04 22:16:14 (145) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-04 22:16:14 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-05 22:13:51 (145) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-05 22:13:51 (1625) [INFO] Checking if your system is up to date: * 2023-05-05 22:13:51 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-05 22:13:51 (3906) [INFO] * 2023-05-05 22:13:51 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-05 22:13:51 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-05 22:13:51 (3919) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-05 22:13:51 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-05 22:13:51 (3919) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-05 22:13:51 (3919) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-05 22:13:51 (3919) [INFO] : wp-toolkit-thirdparties * 2023-05-05 22:13:51 (3919) [INFO] Cleaning up list of fastest mirrors * 2023-05-05 22:13:51 (3919) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-05 22:13:52 (3936) [INFO] * 2023-05-05 22:13:52 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-05 22:13:52 (3906) [INFO] * 2023-05-05 22:13:56 (3919) [INFO] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/ce793e91ead7c5e340f40b89e2707a0c5cfec0ec4ee892a9f3ff44ca28ef2643-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-05 22:13:56 (3919) [INFO] Trying other mirror. * 2023-05-05 22:13:56 (3919) [INFO] To address this issue please refer to the below wiki article * 2023-05-05 22:13:56 (3919) [INFO] * 2023-05-05 22:13:56 (3919) [INFO] https://wiki.centos.org/yum-errors * 2023-05-05 22:13:56 (3919) [INFO] * 2023-05-05 22:13:56 (3919) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-05-05 22:13:56 (3919) [INFO] * 2023-05-05 22:14:12 (3919) [INFO] * 2023-05-05 22:14:12 (3919) [INFO] kernel.x86_64 3.10.0-1160.88.1.el7 updates * 2023-05-05 22:14:12 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-05 22:14:12 (3936) [INFO] * 2023-05-05 22:14:12 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-05 22:14:12 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-05 22:14:35 (1491) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-05 22:14:35 (1492) [ERROR] https://lon.mirror.rackspace.com/epel/7/x86_64/repodata/2dce05be91f327c25ebe14b80ce87fa204b7d4c827579ac233d09ca009aed294-prestodelta.xml.gz: [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://lon.mirror.rackspace.com/epel/7/x86_64/repodata/6fbfc4dbd7307b675aa9d64da2124b4a71804b8229d12e2092837d0241e51faf-other.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2023-05-05 22:14:35 (145) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-05 22:14:35 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-05 22:14:35 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TTrA9LHPSv/ea_profile.json * 2023-05-05 22:14:36 (2090) [INFO] Backed up EA4 profile to /tmp/TTrA9LHPSv/ea_profile.json * 2023-05-05 22:14:37 (145) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-05 22:14:37 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-06 22:15:16 (145) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-06 22:15:16 (1625) [INFO] Checking if your system is up to date: * 2023-05-06 22:15:16 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-06 22:15:16 (3906) [INFO] * 2023-05-06 22:15:16 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-06 22:15:16 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-06 22:15:16 (3919) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-06 22:15:16 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-06 22:15:16 (3919) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-06 22:15:16 (3919) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-06 22:15:16 (3919) [INFO] : wp-toolkit-thirdparties * 2023-05-06 22:15:16 (3919) [INFO] Cleaning up list of fastest mirrors * 2023-05-06 22:15:16 (3919) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-06 22:15:16 (3936) [INFO] * 2023-05-06 22:15:16 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-06 22:15:16 (3906) [INFO] * 2023-05-06 22:15:47 (3919) [INFO] * 2023-05-06 22:15:47 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-06 22:15:47 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-06 22:15:47 (3936) [INFO] * 2023-05-06 22:15:47 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-06 22:15:47 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-06 22:16:11 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-06 22:16:11 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8lZVV_zlpz/ea_profile.json * 2023-05-06 22:16:12 (2090) [INFO] Backed up EA4 profile to /tmp/8lZVV_zlpz/ea_profile.json * 2023-05-06 22:16:12 (145) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-06 22:16:12 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-07 22:14:55 (145) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-07 22:14:55 (1625) [INFO] Checking if your system is up to date: * 2023-05-07 22:14:55 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-07 22:14:55 (3906) [INFO] * 2023-05-07 22:14:56 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-07 22:14:56 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-07 22:14:56 (3919) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-07 22:14:56 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-07 22:14:56 (3919) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-07 22:14:56 (3919) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-07 22:14:56 (3919) [INFO] : wp-toolkit-thirdparties * 2023-05-07 22:14:56 (3919) [INFO] Cleaning up list of fastest mirrors * 2023-05-07 22:14:56 (3919) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-07 22:14:56 (3936) [INFO] * 2023-05-07 22:14:56 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-07 22:14:56 (3906) [INFO] * 2023-05-07 22:15:18 (3919) [INFO] * 2023-05-07 22:15:18 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-07 22:15:18 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-07 22:15:18 (3936) [INFO] * 2023-05-07 22:15:18 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-07 22:15:18 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-07 22:15:40 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-07 22:15:40 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7lq9ckFJ99/ea_profile.json * 2023-05-07 22:15:41 (2090) [INFO] Backed up EA4 profile to /tmp/7lq9ckFJ99/ea_profile.json * 2023-05-07 22:15:41 (145) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-07 22:15:41 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-08 22:14:05 (145) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-08 22:14:05 (1625) [INFO] Checking if your system is up to date: * 2023-05-08 22:14:05 (3905) [INFO] Running: /usr/bin/yum clean all * 2023-05-08 22:14:05 (3906) [INFO] * 2023-05-08 22:14:05 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-08 22:14:05 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-08 22:14:05 (3919) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-08 22:14:05 (3919) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-08 22:14:05 (3919) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-08 22:14:05 (3919) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-08 22:14:05 (3919) [INFO] : wp-toolkit-thirdparties * 2023-05-08 22:14:05 (3919) [INFO] Cleaning up list of fastest mirrors * 2023-05-08 22:14:05 (3919) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-08 22:14:06 (3936) [INFO] * 2023-05-08 22:14:06 (3905) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-08 22:14:06 (3906) [INFO] * 2023-05-08 22:14:27 (3919) [INFO] * 2023-05-08 22:14:27 (3919) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-08 22:14:27 (3919) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-08 22:14:27 (3936) [INFO] * 2023-05-08 22:14:27 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-08 22:14:27 (145) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-08 22:14:48 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-08 22:14:48 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R754qyXhxC/ea_profile.json * 2023-05-08 22:14:49 (2090) [INFO] Backed up EA4 profile to /tmp/R754qyXhxC/ea_profile.json * 2023-05-08 22:14:50 (145) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/cpanel/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-08 22:14:50 (246) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-09 22:14:02 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-09 22:14:02 (1659) [INFO] Checking if your system is up to date: * 2023-05-09 22:14:02 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-09 22:14:02 (3975) [INFO] * 2023-05-09 22:14:02 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-09 22:14:02 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-09 22:14:02 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-09 22:14:02 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 * 2023-05-09 22:14:02 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-09 22:14:02 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-09 22:14:02 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-09 22:14:02 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-09 22:14:02 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-09 22:14:02 (4005) [INFO] * 2023-05-09 22:14:02 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-09 22:14:02 (3975) [INFO] * 2023-05-09 22:14:24 (3988) [INFO] * 2023-05-09 22:14:24 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-09 22:14:24 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-09 22:14:25 (4005) [INFO] * 2023-05-09 22:14:25 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-09 22:14:25 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-09 22:14:48 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-09 22:14:48 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nnurkwFV0o/ea_profile.json * 2023-05-09 22:14:48 (2159) [INFO] Backed up EA4 profile to /tmp/nnurkwFV0o/ea_profile.json * 2023-05-09 22:14:49 (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 22:14:49 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-10 22:15:56 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-10 22:15:56 (1659) [INFO] Checking if your system is up to date: * 2023-05-10 22:15:56 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-10 22:15:56 (3975) [INFO] * 2023-05-10 22:15:56 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-10 22:15:56 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-10 22:15:56 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-10 22:15:56 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-10 22:15:56 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-10 22:15:56 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-10 22:15:56 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-10 22:15:56 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-10 22:15:56 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-10 22:15:56 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-10 22:15:56 (4005) [INFO] * 2023-05-10 22:15:56 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-10 22:15:56 (3975) [INFO] * 2023-05-10 22:16:02 (3988) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-10 22:16:02 (3988) [INFO] Trying other mirror. * 2023-05-10 22:16:02 (3988) [INFO] To address this issue please refer to the below wiki article * 2023-05-10 22:16:02 (3988) [INFO] * 2023-05-10 22:16:02 (3988) [INFO] https://wiki.centos.org/yum-errors * 2023-05-10 22:16:02 (3988) [INFO] * 2023-05-10 22:16:02 (3988) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2023-05-10 22:16:02 (3988) [INFO] * 2023-05-10 22:16:02 (3988) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-10 22:16:02 (3988) [INFO] Trying other mirror. * 2023-05-10 22:16:03 (3988) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found * 2023-05-10 22:16:03 (3988) [INFO] Trying other mirror. * 2023-05-10 22:16:20 (3988) [INFO] * 2023-05-10 22:16:20 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-10 22:16:20 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-10 22:16:20 (4005) [INFO] * 2023-05-10 22:16:20 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-10 22:16:20 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-10 22:16:21 (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-10 22:16:21 (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-10 22:16:21 (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-10 22:16:21 (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-10 22:16:43 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-05-10 22:16:43 (1526) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/repomd.xml: [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://download.imunify360.com/el/7/slot-7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. https://download.imunify360.com/el/7/slot-8/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. * 2023-05-10 22:16:43 (148) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-05-10 22:16:44 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-10 22:16:44 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cRUxaL5edJ/ea_profile.json * 2023-05-10 22:16:46 (2159) [INFO] Backed up EA4 profile to /tmp/cRUxaL5edJ/ea_profile.json * 2023-05-10 22:16:47 (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 22:16:47 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-11 22:14:03 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-11 22:14:03 (1659) [INFO] Checking if your system is up to date: * 2023-05-11 22:14:03 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-11 22:14:03 (3975) [INFO] * 2023-05-11 22:14:03 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-11 22:14:03 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-11 22:14:03 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-11 22:14:03 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-11 22:14:03 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-11 22:14:03 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-11 22:14:03 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-11 22:14:03 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-11 22:14:03 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-11 22:14:04 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-11 22:14:04 (4005) [INFO] * 2023-05-11 22:14:04 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-11 22:14:04 (3975) [INFO] * 2023-05-11 22:14:24 (3988) [INFO] * 2023-05-11 22:14:24 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-11 22:14:24 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-11 22:14:25 (4005) [INFO] * 2023-05-11 22:14:25 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-11 22:14:25 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-11 22:14:27 (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 22:14:27 (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 22:14:27 (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 22:14:27 (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 22:14:51 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-11 22:14:51 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/i_WuTb0nol/ea_profile.json * 2023-05-11 22:14:52 (2159) [INFO] Backed up EA4 profile to /tmp/i_WuTb0nol/ea_profile.json * 2023-05-11 22:14:54 (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 22:14:55 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-12 22:14:09 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-12 22:14:09 (1659) [INFO] Checking if your system is up to date: * 2023-05-12 22:14:09 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-12 22:14:09 (3975) [INFO] * 2023-05-12 22:14:09 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-12 22:14:10 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-12 22:14:10 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-12 22:14:10 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-12 22:14:10 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-12 22:14:10 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-12 22:14:10 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-12 22:14:10 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-12 22:14:10 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-12 22:14:10 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-12 22:14:10 (4005) [INFO] * 2023-05-12 22:14:10 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-12 22:14:10 (3975) [INFO] * 2023-05-12 22:14:31 (3988) [INFO] * 2023-05-12 22:14:31 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-12 22:14:31 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-12 22:14:31 (4005) [INFO] * 2023-05-12 22:14:31 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-12 22:14:31 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-12 22:14:33 (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 22:14:33 (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 22:14:33 (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 22:14:33 (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 22:14:57 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-12 22:14:57 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MSG5_bED76/ea_profile.json * 2023-05-12 22:14:57 (2159) [INFO] Backed up EA4 profile to /tmp/MSG5_bED76/ea_profile.json * 2023-05-12 22:14: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-12 22:14:58 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-13 22:15:01 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-13 22:15:01 (1659) [INFO] Checking if your system is up to date: * 2023-05-13 22:15:01 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-13 22:15:01 (3975) [INFO] * 2023-05-13 22:15:01 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-13 22:15:01 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-13 22:15:01 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-13 22:15:01 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-13 22:15:01 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-13 22:15:01 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-13 22:15:01 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-13 22:15:01 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-13 22:15:01 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-13 22:15:01 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-13 22:15:02 (4005) [INFO] * 2023-05-13 22:15:02 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-13 22:15:02 (3975) [INFO] * 2023-05-13 22:15:40 (3988) [INFO] * 2023-05-13 22:15:40 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-13 22:15:40 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-13 22:15:40 (4005) [INFO] * 2023-05-13 22:15:40 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-13 22:15:40 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-13 22:15: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-13 22:15: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-13 22:15: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-13 22:15: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-13 22:16:05 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-13 22:16:05 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Sgil8TYOcY/ea_profile.json * 2023-05-13 22:16:06 (2159) [INFO] Backed up EA4 profile to /tmp/Sgil8TYOcY/ea_profile.json * 2023-05-13 22:16:06 (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 22:16:06 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-14 22:14:56 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-14 22:14:56 (1659) [INFO] Checking if your system is up to date: * 2023-05-14 22:14:56 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-14 22:14:56 (3975) [INFO] * 2023-05-14 22:14:56 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-14 22:14:56 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-14 22:14:56 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-14 22:14:56 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-14 22:14:56 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-14 22:14:56 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-14 22:14:56 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-14 22:14:56 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-14 22:14:57 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-14 22:14:57 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-14 22:14:57 (4005) [INFO] * 2023-05-14 22:14:57 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-14 22:14:57 (3975) [INFO] * 2023-05-14 22:15:19 (3988) [INFO] * 2023-05-14 22:15:19 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-14 22:15:19 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-14 22:15:20 (4005) [INFO] * 2023-05-14 22:15:20 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-14 22:15:20 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-14 22:15:22 (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 22:15:22 (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 22:15:22 (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 22:15:22 (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 22:15:44 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-14 22:15:44 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0Lu31CjYHw/ea_profile.json * 2023-05-14 22:15:45 (2159) [INFO] Backed up EA4 profile to /tmp/0Lu31CjYHw/ea_profile.json * 2023-05-14 22:15:46 (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 22:15:46 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-15 22:14:00 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-15 22:14:00 (1659) [INFO] Checking if your system is up to date: * 2023-05-15 22:14:00 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-15 22:14:00 (3975) [INFO] * 2023-05-15 22:14:00 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-15 22:14:00 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-15 22:14:00 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-15 22:14:00 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-15 22:14:00 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-15 22:14:00 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-15 22:14:00 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-15 22:14:00 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-15 22:14:00 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-15 22:14:00 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-15 22:14:00 (4005) [INFO] * 2023-05-15 22:14:00 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-15 22:14:00 (3975) [INFO] * 2023-05-15 22:14:23 (3988) [INFO] * 2023-05-15 22:14:23 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-15 22:14:23 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-15 22:14:23 (4005) [INFO] * 2023-05-15 22:14:23 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-15 22:14:23 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-15 22:14:25 (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 22:14:25 (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 22:14:25 (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 22:14:25 (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 22:14:48 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-15 22:14:48 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yvrjCwZ_jy/ea_profile.json * 2023-05-15 22:14:49 (2159) [INFO] Backed up EA4 profile to /tmp/yvrjCwZ_jy/ea_profile.json * 2023-05-15 22:14:50 (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 22:14:50 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-16 22:14:07 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-16 22:14:07 (1659) [INFO] Checking if your system is up to date: * 2023-05-16 22:14:07 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-16 22:14:07 (3975) [INFO] * 2023-05-16 22:14:07 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-16 22:14:07 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-16 22:14:07 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-16 22:14:07 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-16 22:14:07 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-16 22:14:07 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-16 22:14:07 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-16 22:14:07 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-16 22:14:08 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-16 22:14:08 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-16 22:14:08 (4005) [INFO] * 2023-05-16 22:14:08 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-16 22:14:08 (3975) [INFO] * 2023-05-16 22:14:31 (3988) [INFO] * 2023-05-16 22:14:31 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-16 22:14:31 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-16 22:14:31 (4005) [INFO] * 2023-05-16 22:14:31 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-16 22:14:31 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-16 22:14:33 (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 22:14:33 (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 22:14:33 (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 22:14:33 (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 22:14:56 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-16 22:14:56 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h3lDMg6GYP/ea_profile.json * 2023-05-16 22:14:57 (2159) [INFO] Backed up EA4 profile to /tmp/h3lDMg6GYP/ea_profile.json * 2023-05-16 22:14:57 (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 22:14:57 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-17 22:15:27 (148) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-17 22:15:27 (1659) [INFO] Checking if your system is up to date: * 2023-05-17 22:15:27 (3974) [INFO] Running: /usr/bin/yum clean all * 2023-05-17 22:15:27 (3975) [INFO] * 2023-05-17 22:15:27 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-17 22:15:27 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-17 22:15:27 (3988) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-17 22:15:27 (3988) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-17 22:15:27 (3988) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-17 22:15:27 (3988) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-17 22:15:27 (3988) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-17 22:15:27 (3988) [INFO] : wp-toolkit-thirdparties * 2023-05-17 22:15:27 (3988) [INFO] Cleaning up list of fastest mirrors * 2023-05-17 22:15:27 (3988) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-17 22:15:27 (4005) [INFO] * 2023-05-17 22:15:27 (3974) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-17 22:15:27 (3975) [INFO] * 2023-05-17 22:15:55 (3988) [INFO] * 2023-05-17 22:15:55 (3988) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-17 22:15:55 (3988) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-17 22:15:55 (4005) [INFO] * 2023-05-17 22:15:55 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-17 22:15:55 (148) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-17 22:15:56 (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 22:15:56 (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 22:15:56 (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 22:15:56 (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 22:16:22 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-17 22:16:22 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IkczkE9jkF/ea_profile.json * 2023-05-17 22:16:23 (2159) [INFO] Backed up EA4 profile to /tmp/IkczkE9jkF/ea_profile.json * 2023-05-17 22:16:24 (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 22:16:24 (251) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-18 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-18 22:14:20 (1699) [INFO] Checking if your system is up to date: * 2023-05-18 22:14:20 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-18 22:14:20 (4086) [INFO] * 2023-05-18 22:14:20 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-18 22:14:20 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-18 22:14:20 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-18 22:14:20 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-18 22:14:20 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-18 22:14:20 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-18 22:14:20 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-18 22:14:20 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-18 22:14:20 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-18 22:14:20 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-18 22:14:20 (4116) [INFO] * 2023-05-18 22:14:20 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-18 22:14:20 (4086) [INFO] * 2023-05-18 22:14:52 (4099) [INFO] * 2023-05-18 22:14:52 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-18 22:14:52 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-18 22:14:52 (4116) [INFO] * 2023-05-18 22:14:52 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-18 22:14:52 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-18 22:15:16 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-18 22:15:16 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bJF2RI5cAQ/ea_profile.json * 2023-05-18 22:15:17 (2258) [INFO] Backed up EA4 profile to /tmp/bJF2RI5cAQ/ea_profile.json * 2023-05-18 22:15: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-18 22:15:18 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-19 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-19 22:14:08 (1699) [INFO] Checking if your system is up to date: * 2023-05-19 22:14:08 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-19 22:14:08 (4086) [INFO] * 2023-05-19 22:14:08 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-19 22:14:08 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-19 22:14:08 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-19 22:14:08 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-19 22:14:08 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-19 22:14:08 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-19 22:14:08 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-19 22:14:08 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-19 22:14:08 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-19 22:14:08 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-19 22:14:08 (4116) [INFO] * 2023-05-19 22:14:08 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-19 22:14:08 (4086) [INFO] * 2023-05-19 22:14:30 (4099) [INFO] * 2023-05-19 22:14:30 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-19 22:14:30 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-19 22:14:30 (4116) [INFO] * 2023-05-19 22:14:30 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-19 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-19 22:14:54 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-19 22:14:54 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z0WGlcvDf5/ea_profile.json * 2023-05-19 22:14:55 (2258) [INFO] Backed up EA4 profile to /tmp/z0WGlcvDf5/ea_profile.json * 2023-05-19 22:14: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-05-19 22:14:56 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-20 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-20 22:15:14 (1699) [INFO] Checking if your system is up to date: * 2023-05-20 22:15:14 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-20 22:15:14 (4086) [INFO] * 2023-05-20 22:15:15 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-20 22:15:15 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-20 22:15:15 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-20 22:15:15 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-20 22:15:15 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-20 22:15:15 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-20 22:15:15 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-20 22:15:15 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-20 22:15:15 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-20 22:15:15 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-20 22:15:15 (4116) [INFO] * 2023-05-20 22:15:15 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-20 22:15:15 (4086) [INFO] * 2023-05-20 22:15:49 (4099) [INFO] * 2023-05-20 22:15:49 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-20 22:15:49 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-20 22:15:49 (4116) [INFO] * 2023-05-20 22:15:49 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-20 22:15:49 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-20 22:16:11 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-20 22:16:11 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EOTGw6ItVQ/ea_profile.json * 2023-05-20 22:16:12 (2258) [INFO] Backed up EA4 profile to /tmp/EOTGw6ItVQ/ea_profile.json * 2023-05-20 22:16: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-05-20 22:16:13 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-21 22:15:03 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-21 22:15:03 (1699) [INFO] Checking if your system is up to date: * 2023-05-21 22:15:03 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-21 22:15:03 (4086) [INFO] * 2023-05-21 22:15:03 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-21 22:15:03 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-21 22:15:03 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-21 22:15:03 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-21 22:15:03 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-21 22:15:03 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-21 22:15:03 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-21 22:15:03 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-21 22:15:04 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-21 22:15:04 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-21 22:15:04 (4116) [INFO] * 2023-05-21 22:15:04 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-21 22:15:04 (4086) [INFO] * 2023-05-21 22:15:31 (4099) [INFO] * 2023-05-21 22:15:31 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-21 22:15:31 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-21 22:15:31 (4116) [INFO] * 2023-05-21 22:15:31 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-21 22:15:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-21 22:15:55 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-21 22:15:55 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rdYr9sYhPs/ea_profile.json * 2023-05-21 22:15:56 (2258) [INFO] Backed up EA4 profile to /tmp/rdYr9sYhPs/ea_profile.json * 2023-05-21 22:15: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-05-21 22:15:56 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-22 22:14:45 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-22 22:14:45 (1699) [INFO] Checking if your system is up to date: * 2023-05-22 22:14:45 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-22 22:14:45 (4086) [INFO] * 2023-05-22 22:14:45 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-22 22:14:45 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-22 22:14:45 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-22 22:14:45 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-22 22:14:45 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-22 22:14:45 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-22 22:14:45 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-22 22:14:45 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-22 22:14:45 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-22 22:14:45 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-22 22:14:45 (4116) [INFO] * 2023-05-22 22:14:45 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-22 22:14:45 (4086) [INFO] * 2023-05-22 22:15:10 (4099) [INFO] * 2023-05-22 22:15:10 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-22 22:15:10 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-22 22:15:10 (4116) [INFO] * 2023-05-22 22:15:10 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-22 22:15:10 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-22 22:15:35 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-22 22:15:35 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sh8JOJV4yQ/ea_profile.json * 2023-05-22 22:15:35 (2258) [INFO] Backed up EA4 profile to /tmp/sh8JOJV4yQ/ea_profile.json * 2023-05-22 22:15:36 (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 22:15:36 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-23 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-23 22:14:07 (1699) [INFO] Checking if your system is up to date: * 2023-05-23 22:14:07 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-23 22:14:07 (4086) [INFO] * 2023-05-23 22:14:08 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-23 22:14:08 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-23 22:14:08 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-23 22:14:08 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-23 22:14:08 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-23 22:14:08 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-23 22:14:08 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-23 22:14:08 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-23 22:14:08 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-23 22:14:08 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-23 22:14:08 (4116) [INFO] * 2023-05-23 22:14:08 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-23 22:14:08 (4086) [INFO] * 2023-05-23 22:14:31 (4099) [INFO] * 2023-05-23 22:14:31 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-23 22:14:31 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-23 22:14:31 (4116) [INFO] * 2023-05-23 22:14:31 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-23 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-23 22:14:59 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-23 22:14:59 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2EYIUrwG4d/ea_profile.json * 2023-05-23 22:15:00 (2258) [INFO] Backed up EA4 profile to /tmp/2EYIUrwG4d/ea_profile.json * 2023-05-23 22:15: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-23 22:15:01 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-24 22:14:02 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-24 22:14:02 (1699) [INFO] Checking if your system is up to date: * 2023-05-24 22:14:02 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-24 22:14:02 (4086) [INFO] * 2023-05-24 22:14:02 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-24 22:14:02 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-24 22:14:02 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-24 22:14:02 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-24 22:14:02 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-24 22:14:02 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-24 22:14:02 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-24 22:14:02 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-24 22:14:02 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-24 22:14:02 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-24 22:14:02 (4116) [INFO] * 2023-05-24 22:14:02 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-24 22:14:02 (4086) [INFO] * 2023-05-24 22:14:24 (4099) [INFO] * 2023-05-24 22:14:24 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-24 22:14:24 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-24 22:14:24 (4116) [INFO] * 2023-05-24 22:14:24 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-24 22:14:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-24 22:14:47 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-24 22:14:47 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9On_jYEE_p/ea_profile.json * 2023-05-24 22:14:48 (2258) [INFO] Backed up EA4 profile to /tmp/9On_jYEE_p/ea_profile.json * 2023-05-24 22:14: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-05-24 22:14:49 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-25 22:15:33 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-25 22:15:33 (1699) [INFO] Checking if your system is up to date: * 2023-05-25 22:15:33 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-25 22:15:33 (4086) [INFO] * 2023-05-25 22:15:34 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-25 22:15:34 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-25 22:15:34 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-25 22:15:34 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-25 22:15:34 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-25 22:15:34 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-25 22:15:34 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-25 22:15:34 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-25 22:15:34 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-25 22:15:34 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-25 22:15:34 (4116) [INFO] * 2023-05-25 22:15:34 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-25 22:15:34 (4086) [INFO] * 2023-05-25 22:15:57 (4099) [INFO] * 2023-05-25 22:15:57 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-25 22:15:57 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-25 22:15:57 (4116) [INFO] * 2023-05-25 22:15:57 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-25 22:15:57 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-25 22:16:23 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-25 22:16:23 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XSP28yc3wc/ea_profile.json * 2023-05-25 22:16:24 (2258) [INFO] Backed up EA4 profile to /tmp/XSP28yc3wc/ea_profile.json * 2023-05-25 22:16: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-25 22:16:25 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-26 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-26 22:14:08 (1699) [INFO] Checking if your system is up to date: * 2023-05-26 22:14:08 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-26 22:14:08 (4086) [INFO] * 2023-05-26 22:14:08 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-26 22:14:08 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-26 22:14:08 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-26 22:14:08 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-26 22:14:08 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-26 22:14:08 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-26 22:14:08 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-26 22:14:08 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-26 22:14:08 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-26 22:14:08 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-26 22:14:08 (4116) [INFO] * 2023-05-26 22:14:08 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-26 22:14:08 (4086) [INFO] * 2023-05-26 22:14:30 (4099) [INFO] * 2023-05-26 22:14:30 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-26 22:14:30 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-26 22:14:30 (4116) [INFO] * 2023-05-26 22:14:30 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-26 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-26 22:14:57 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-26 22:14:57 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jvBUsB2jv3/ea_profile.json * 2023-05-26 22:14:58 (2258) [INFO] Backed up EA4 profile to /tmp/jvBUsB2jv3/ea_profile.json * 2023-05-26 22:14: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-05-26 22:14:59 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-27 22:15:00 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-27 22:15:00 (1699) [INFO] Checking if your system is up to date: * 2023-05-27 22:15:00 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-27 22:15:00 (4086) [INFO] * 2023-05-27 22:15:00 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-27 22:15:01 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-27 22:15:01 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-27 22:15:01 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-27 22:15:01 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-27 22:15:01 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-27 22:15:01 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-27 22:15:01 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-27 22:15:02 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-27 22:15:02 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-27 22:15:02 (4116) [INFO] * 2023-05-27 22:15:02 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-27 22:15:02 (4086) [INFO] * 2023-05-27 22:15:27 (4099) [INFO] * 2023-05-27 22:15:27 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-27 22:15:27 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-27 22:15:27 (4116) [INFO] * 2023-05-27 22:15:27 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-27 22:15:27 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-27 22:15:49 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-27 22:15:49 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RytBJbqWBn/ea_profile.json * 2023-05-27 22:15:50 (2258) [INFO] Backed up EA4 profile to /tmp/RytBJbqWBn/ea_profile.json * 2023-05-27 22:15: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-05-27 22:15:51 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-28 22:14:59 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-28 22:14:59 (1699) [INFO] Checking if your system is up to date: * 2023-05-28 22:14:59 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-28 22:14:59 (4086) [INFO] * 2023-05-28 22:14:59 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-28 22:14:59 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-28 22:14:59 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-28 22:14:59 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-28 22:14:59 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-28 22:14:59 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-28 22:14:59 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-28 22:14:59 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-28 22:14:59 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-28 22:14:59 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-28 22:15:00 (4116) [INFO] * 2023-05-28 22:15:00 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-28 22:15:00 (4086) [INFO] * 2023-05-28 22:15:23 (4099) [INFO] * 2023-05-28 22:15:23 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-28 22:15:23 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-28 22:15:23 (4116) [INFO] * 2023-05-28 22:15:23 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-28 22:15:23 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-28 22:15:54 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-28 22:15:54 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SbkgH0D_Rn/ea_profile.json * 2023-05-28 22:15:55 (2258) [INFO] Backed up EA4 profile to /tmp/SbkgH0D_Rn/ea_profile.json * 2023-05-28 22:15: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-05-28 22:15:56 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-29 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-29 22:14:04 (1699) [INFO] Checking if your system is up to date: * 2023-05-29 22:14:04 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-29 22:14:04 (4086) [INFO] * 2023-05-29 22:14:04 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-29 22:14:04 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-29 22:14:04 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-29 22:14:04 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-29 22:14:04 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-29 22:14:04 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-29 22:14:04 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-29 22:14:04 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-29 22:14:04 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-29 22:14:04 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-29 22:14:04 (4116) [INFO] * 2023-05-29 22:14:04 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-29 22:14:04 (4086) [INFO] * 2023-05-29 22:14:26 (4099) [INFO] * 2023-05-29 22:14:26 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-29 22:14:26 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-29 22:14:26 (4116) [INFO] * 2023-05-29 22:14:26 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-29 22:14:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-29 22:14:50 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-29 22:14:50 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TvEC3OtCgX/ea_profile.json * 2023-05-29 22:14:51 (2258) [INFO] Backed up EA4 profile to /tmp/TvEC3OtCgX/ea_profile.json * 2023-05-29 22:14: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-05-29 22:14:52 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-30 22:13:55 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-30 22:13:55 (1699) [INFO] Checking if your system is up to date: * 2023-05-30 22:13:55 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-30 22:13:55 (4086) [INFO] * 2023-05-30 22:13:55 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-30 22:13:55 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-30 22:13:55 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-30 22:13:55 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-30 22:13:55 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-30 22:13:55 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-30 22:13:55 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-30 22:13:55 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-30 22:13:55 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-30 22:13:55 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-30 22:13:56 (4116) [INFO] * 2023-05-30 22:13:56 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-30 22:13:56 (4086) [INFO] * 2023-05-30 22:14:17 (4099) [INFO] * 2023-05-30 22:14:17 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-30 22:14:17 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-30 22:14:17 (4116) [INFO] * 2023-05-30 22:14:17 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-30 22:14:17 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-30 22:14:41 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-30 22:14:41 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0RnIkuUlpF/ea_profile.json * 2023-05-30 22:14:42 (2258) [INFO] Backed up EA4 profile to /tmp/0RnIkuUlpF/ea_profile.json * 2023-05-30 22:14: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-05-30 22:14:43 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-05-31 22:16:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-05-31 22:16:06 (1699) [INFO] Checking if your system is up to date: * 2023-05-31 22:16:06 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-05-31 22:16:06 (4086) [INFO] * 2023-05-31 22:16:06 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-05-31 22:16:06 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-05-31 22:16:06 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-05-31 22:16:06 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-05-31 22:16:06 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-05-31 22:16:06 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-05-31 22:16:06 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-05-31 22:16:06 (4099) [INFO] : wp-toolkit-thirdparties * 2023-05-31 22:16:06 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-05-31 22:16:06 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-05-31 22:16:06 (4116) [INFO] * 2023-05-31 22:16:06 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-05-31 22:16:06 (4086) [INFO] * 2023-05-31 22:16:32 (4099) [INFO] * 2023-05-31 22:16:32 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-05-31 22:16:32 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-05-31 22:16:32 (4116) [INFO] * 2023-05-31 22:16:32 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-05-31 22:16:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-05-31 22:16:56 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-05-31 22:16:56 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fja3D3YYL3/ea_profile.json * 2023-05-31 22:16:57 (2258) [INFO] Backed up EA4 profile to /tmp/fja3D3YYL3/ea_profile.json * 2023-05-31 22:16: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-05-31 22:16:59 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-06-01 22:15:29 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-01 22:15:29 (1699) [INFO] Checking if your system is up to date: * 2023-06-01 22:15:29 (4085) [INFO] Running: /usr/bin/yum clean all * 2023-06-01 22:15:29 (4086) [INFO] * 2023-06-01 22:15:29 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-01 22:15:30 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-01 22:15:30 (4099) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-01 22:15:30 (4099) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-01 22:15:30 (4099) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-01 22:15:30 (4099) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-01 22:15:30 (4099) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-01 22:15:30 (4099) [INFO] : wp-toolkit-thirdparties * 2023-06-01 22:15:30 (4099) [INFO] Cleaning up list of fastest mirrors * 2023-06-01 22:15:30 (4099) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-01 22:15:30 (4116) [INFO] * 2023-06-01 22:15:30 (4085) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-01 22:15:30 (4086) [INFO] * 2023-06-01 22:16:00 (4099) [INFO] * 2023-06-01 22:16:00 (4099) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-01 22:16:00 (4099) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-01 22:16:00 (4116) [INFO] * 2023-06-01 22:16:00 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-01 22:16:00 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-01 22:16:22 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-01 22:16:22 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/myJjUJhKhA/ea_profile.json * 2023-06-01 22:16:22 (2258) [INFO] Backed up EA4 profile to /tmp/myJjUJhKhA/ea_profile.json * 2023-06-01 22:16: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-01 22:16:23 (258) [WARN] Please fix the detected issues before performing the elevation process. * 2023-06-02 22:14:00 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-02 22:14:00 (1700) [INFO] Checking if your system is up to date: * 2023-06-02 22:14:00 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-02 22:14:00 (4089) [INFO] * 2023-06-02 22:14:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-02 22:14:01 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-02 22:14:01 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-02 22:14:01 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-02 22:14:01 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-02 22:14:01 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-02 22:14:01 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-02 22:14:01 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-02 22:14:01 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-02 22:14:01 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-02 22:14:01 (4119) [INFO] * 2023-06-02 22:14:01 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-02 22:14:01 (4089) [INFO] * 2023-06-02 22:14:24 (4102) [INFO] * 2023-06-02 22:14:24 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-02 22:14:24 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-02 22:14:24 (4119) [INFO] * 2023-06-02 22:14:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-02 22:14:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-02 22:14:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-02 22:14:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j4ktvkDeul/ea_profile.json * 2023-06-02 22:14:48 (2259) [INFO] Backed up EA4 profile to /tmp/j4ktvkDeul/ea_profile.json * 2023-06-02 22:14: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-06-02 22:14:49 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-03 22:15:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-03 22:15:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-03 22:15:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-03 22:15:06 (4089) [INFO] * 2023-06-03 22:15:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-03 22:15:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-03 22:15:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-03 22:15:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-03 22:15:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-03 22:15:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-03 22:15:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-03 22:15:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-03 22:15:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-03 22:15:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-03 22:15:06 (4119) [INFO] * 2023-06-03 22:15:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-03 22:15:06 (4089) [INFO] * 2023-06-03 22:15:32 (4102) [INFO] * 2023-06-03 22:15:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-03 22:15:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-03 22:15:32 (4119) [INFO] * 2023-06-03 22:15:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-03 22:15:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-03 22:15:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-03 22:15:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rUyx4FqdGZ/ea_profile.json * 2023-06-03 22:15:55 (2259) [INFO] Backed up EA4 profile to /tmp/rUyx4FqdGZ/ea_profile.json * 2023-06-03 22:15: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-03 22:15:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-04 22:14:54 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-04 22:14:54 (1700) [INFO] Checking if your system is up to date: * 2023-06-04 22:14:54 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-04 22:14:54 (4089) [INFO] * 2023-06-04 22:14:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-04 22:14:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-04 22:14:56 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-04 22:14:56 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-04 22:14:56 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-04 22:14:56 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-04 22:14:56 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-04 22:14:56 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-04 22:14:56 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-04 22:14:56 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-04 22:14:56 (4119) [INFO] * 2023-06-04 22:14:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-04 22:14:56 (4089) [INFO] * 2023-06-04 22:15:21 (4102) [INFO] * 2023-06-04 22:15:21 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-04 22:15:21 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-04 22:15:21 (4119) [INFO] * 2023-06-04 22:15:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-04 22:15:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-04 22:15:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-04 22:15:43 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0jz7aLBkae/ea_profile.json * 2023-06-04 22:15:44 (2259) [INFO] Backed up EA4 profile to /tmp/0jz7aLBkae/ea_profile.json * 2023-06-04 22:15: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-04 22:15:44 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-05 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-05 22:14:36 (1700) [INFO] Checking if your system is up to date: * 2023-06-05 22:14:36 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-05 22:14:36 (4089) [INFO] * 2023-06-05 22:14:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-05 22:14:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-05 22:14:36 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-05 22:14:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-05 22:14:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-05 22:14:36 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-05 22:14:36 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-05 22:14:36 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-05 22:14:36 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-05 22:14:36 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-05 22:14:36 (4119) [INFO] * 2023-06-05 22:14:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-05 22:14:36 (4089) [INFO] * 2023-06-05 22:15:00 (4102) [INFO] * 2023-06-05 22:15:00 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-05 22:15:00 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-05 22:15:00 (4119) [INFO] * 2023-06-05 22:15:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-05 22:15:00 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-05 22:15:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-05 22:15:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WfaJN_r4J8/ea_profile.json * 2023-06-05 22:15:24 (2259) [INFO] Backed up EA4 profile to /tmp/WfaJN_r4J8/ea_profile.json * 2023-06-05 22:15: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-05 22:15:25 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-06 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-06 22:14:05 (1700) [INFO] Checking if your system is up to date: * 2023-06-06 22:14:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-06 22:14:05 (4089) [INFO] * 2023-06-06 22:14:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-06 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-06 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-06 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-06 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-06 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-06 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-06 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-06 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-06 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-06 22:14:06 (4119) [INFO] * 2023-06-06 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-06 22:14:06 (4089) [INFO] * 2023-06-06 22:14:27 (4102) [INFO] * 2023-06-06 22:14:27 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-06 22:14:27 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-06 22:14:27 (4119) [INFO] * 2023-06-06 22:14:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-06 22:14:27 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-06 22:14:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-06 22:14:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kao4m5PLSW/ea_profile.json * 2023-06-06 22:14:51 (2259) [INFO] Backed up EA4 profile to /tmp/Kao4m5PLSW/ea_profile.json * 2023-06-06 22:14: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-06-06 22:14:52 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-07 22:14:46 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-07 22:14:46 (1700) [INFO] Checking if your system is up to date: * 2023-06-07 22:14:46 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-07 22:14:46 (4089) [INFO] * 2023-06-07 22:14:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-07 22:14:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-07 22:14:46 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-07 22:14:46 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-07 22:14:46 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-07 22:14:46 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-07 22:14:46 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-07 22:14:46 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-07 22:14:46 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-07 22:14:46 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-07 22:14:46 (4119) [INFO] * 2023-06-07 22:14:46 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-07 22:14:46 (4089) [INFO] * 2023-06-07 22:15:13 (4102) [INFO] * 2023-06-07 22:15:13 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-07 22:15:13 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-07 22:15:14 (4119) [INFO] * 2023-06-07 22:15:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-07 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-07 22:15:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-07 22:15:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NS09U1DwH9/ea_profile.json * 2023-06-07 22:15:38 (2259) [INFO] Backed up EA4 profile to /tmp/NS09U1DwH9/ea_profile.json * 2023-06-07 22:15: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-07 22:15:39 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-08 22:14:03 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-08 22:14:03 (1700) [INFO] Checking if your system is up to date: * 2023-06-08 22:14:03 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-08 22:14:03 (4089) [INFO] * 2023-06-08 22:14:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-08 22:14:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-08 22:14:03 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-08 22:14:03 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-08 22:14:03 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-08 22:14:03 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-08 22:14:03 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-08 22:14:03 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-08 22:14:03 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-08 22:14:03 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-08 22:14:03 (4119) [INFO] * 2023-06-08 22:14:03 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-08 22:14:03 (4089) [INFO] * 2023-06-08 22:14:26 (4102) [INFO] * 2023-06-08 22:14:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-08 22:14:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-08 22:14:26 (4119) [INFO] * 2023-06-08 22:14:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-08 22:14:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-08 22:14:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-08 22:14:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YbOcIhnNC2/ea_profile.json * 2023-06-08 22:14:50 (2259) [INFO] Backed up EA4 profile to /tmp/YbOcIhnNC2/ea_profile.json * 2023-06-08 22:14: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-06-08 22:14:51 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-09 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-09 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-09 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-09 22:14:06 (4089) [INFO] * 2023-06-09 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-09 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-09 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-09 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-09 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-09 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-09 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-09 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-09 22:14:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-09 22:14:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-09 22:14:07 (4119) [INFO] * 2023-06-09 22:14:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-09 22:14:07 (4089) [INFO] * 2023-06-09 22:14:32 (4102) [INFO] * 2023-06-09 22:14:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-09 22:14:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-09 22:14:32 (4119) [INFO] * 2023-06-09 22:14:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-09 22:14:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-09 22:14:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-09 22:14:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ergsl0MxpA/ea_profile.json * 2023-06-09 22:14:57 (2259) [INFO] Backed up EA4 profile to /tmp/Ergsl0MxpA/ea_profile.json * 2023-06-09 22:14: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-06-09 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-10 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-10 22:15:09 (1700) [INFO] Checking if your system is up to date: * 2023-06-10 22:15:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-10 22:15:09 (4089) [INFO] * 2023-06-10 22:15:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-10 22:15:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-10 22:15:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-10 22:15:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-10 22:15:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-10 22:15:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-10 22:15:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-10 22:15:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-10 22:15:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-10 22:15:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-10 22:15:10 (4119) [INFO] * 2023-06-10 22:15:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-10 22:15:10 (4089) [INFO] * 2023-06-10 22:15:35 (4102) [INFO] * 2023-06-10 22:15:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-10 22:15:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-10 22:15:35 (4119) [INFO] * 2023-06-10 22:15:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-10 22:15:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-10 22:16:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-10 22:16:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VgtxLrw4QS/ea_profile.json * 2023-06-10 22:16:05 (2259) [INFO] Backed up EA4 profile to /tmp/VgtxLrw4QS/ea_profile.json * 2023-06-10 22:16: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-06-10 22:16:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-11 22:14:58 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-11 22:14:59 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-11 22:14:59 (1700) [INFO] Checking if your system is up to date: * 2023-06-11 22:14:59 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-11 22:14:59 (4089) [INFO] * 2023-06-11 22:14:59 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-11 22:14:59 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-11 22:14:59 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-11 22:14:59 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-11 22:14:59 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-11 22:14:59 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-11 22:14:59 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-11 22:14:59 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-11 22:14:59 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-11 22:14:59 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-11 22:14:59 (4119) [INFO] * 2023-06-11 22:14:59 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-11 22:14:59 (4089) [INFO] * 2023-06-11 22:15:23 (4102) [INFO] * 2023-06-11 22:15:23 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-11 22:15:23 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-11 22:15:23 (4119) [INFO] * 2023-06-11 22:15:23 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-11 22:15:23 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-11 22:15:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-11 22:15:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/64lpM7rML5/ea_profile.json * 2023-06-11 22:15:46 (2259) [INFO] Backed up EA4 profile to /tmp/64lpM7rML5/ea_profile.json * 2023-06-11 22:15: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-06-11 22:15:46 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-12 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-12 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-12 22:14:04 (1700) [INFO] Checking if your system is up to date: * 2023-06-12 22:14:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-12 22:14:04 (4089) [INFO] * 2023-06-12 22:14:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-12 22:14:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-12 22:14:05 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-12 22:14:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-12 22:14:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-12 22:14:05 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-12 22:14:05 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-12 22:14:05 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-12 22:14:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-12 22:14:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-12 22:14:05 (4119) [INFO] * 2023-06-12 22:14:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-12 22:14:05 (4089) [INFO] * 2023-06-12 22:14:30 (4102) [INFO] * 2023-06-12 22:14:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-12 22:14:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-12 22:14:30 (4119) [INFO] * 2023-06-12 22:14:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-12 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-12 22:14:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-12 22:14:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1_7xj89Qu7/ea_profile.json * 2023-06-12 22:14:55 (2259) [INFO] Backed up EA4 profile to /tmp/1_7xj89Qu7/ea_profile.json * 2023-06-12 22:14: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-12 22:14:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-13 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-13 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-13 22:14:05 (1700) [INFO] Checking if your system is up to date: * 2023-06-13 22:14:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-13 22:14:05 (4089) [INFO] * 2023-06-13 22:14:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-13 22:14:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-13 22:14:05 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-13 22:14:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-13 22:14:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-13 22:14:05 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-13 22:14:05 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-13 22:14:05 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-13 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-13 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-13 22:14:08 (4119) [INFO] * 2023-06-13 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-13 22:14:08 (4089) [INFO] * 2023-06-13 22:14:31 (4102) [INFO] * 2023-06-13 22:14:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-13 22:14:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-13 22:14:31 (4119) [INFO] * 2023-06-13 22:14:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-13 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-13 22:14:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-13 22:14:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/clQopry0Xj/ea_profile.json * 2023-06-13 22:14:56 (2259) [INFO] Backed up EA4 profile to /tmp/clQopry0Xj/ea_profile.json * 2023-06-13 22:14: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-13 22:14:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-14 22:15:48 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-14 22:15:49 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-14 22:15:49 (1700) [INFO] Checking if your system is up to date: * 2023-06-14 22:15:49 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-14 22:15:49 (4089) [INFO] * 2023-06-14 22:15:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-14 22:15:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-14 22:15:50 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-14 22:15:50 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-14 22:15:50 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-14 22:15:50 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-14 22:15:50 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-14 22:15:50 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-14 22:15:52 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-14 22:15:52 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-14 22:15:52 (4119) [INFO] * 2023-06-14 22:15:52 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-14 22:15:52 (4089) [INFO] * 2023-06-14 22:16:16 (4102) [INFO] * 2023-06-14 22:16:16 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-14 22:16:16 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-14 22:16:16 (4119) [INFO] * 2023-06-14 22:16:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-14 22:16:16 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-14 22:16:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-14 22:16:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bLE7lv4BKp/ea_profile.json * 2023-06-14 22:16:40 (2259) [INFO] Backed up EA4 profile to /tmp/bLE7lv4BKp/ea_profile.json * 2023-06-14 22:16: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-06-14 22:16:41 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-15 22:14:02 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-15 22:14:03 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-15 22:14:03 (1700) [INFO] Checking if your system is up to date: * 2023-06-15 22:14:03 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-15 22:14:03 (4089) [INFO] * 2023-06-15 22:14:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-15 22:14:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-15 22:14:04 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-15 22:14:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-15 22:14:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-15 22:14:04 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-15 22:14:04 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-15 22:14:04 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-15 22:14:04 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-15 22:14:04 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-15 22:14:04 (4119) [INFO] * 2023-06-15 22:14:04 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-15 22:14:04 (4089) [INFO] * 2023-06-15 22:14:27 (4102) [INFO] * 2023-06-15 22:14:27 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-15 22:14:27 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-15 22:14:27 (4119) [INFO] * 2023-06-15 22:14:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-15 22:14:27 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-15 22:14:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-15 22:14:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/77hGnteVX5/ea_profile.json * 2023-06-15 22:14:50 (2259) [INFO] Backed up EA4 profile to /tmp/77hGnteVX5/ea_profile.json * 2023-06-15 22:14: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-06-15 22:14:51 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-16 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-16 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-16 22:14:09 (1700) [INFO] Checking if your system is up to date: * 2023-06-16 22:14:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-16 22:14:09 (4089) [INFO] * 2023-06-16 22:14:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-16 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-16 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-16 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-16 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-16 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-16 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-16 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-16 22:14:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-16 22:14:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-16 22:14:10 (4119) [INFO] * 2023-06-16 22:14:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-16 22:14:10 (4089) [INFO] * 2023-06-16 22:14:35 (4102) [INFO] * 2023-06-16 22:14:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-16 22:14:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-16 22:14:35 (4119) [INFO] * 2023-06-16 22:14:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-16 22:14:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-16 22:15:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-16 22:15:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8A1v4_jXYM/ea_profile.json * 2023-06-16 22:15:01 (2259) [INFO] Backed up EA4 profile to /tmp/8A1v4_jXYM/ea_profile.json * 2023-06-16 22:15: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-06-16 22:15:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-17 22:15:04 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-17 22:15:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-17 22:15:05 (1700) [INFO] Checking if your system is up to date: * 2023-06-17 22:15:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-17 22:15:05 (4089) [INFO] * 2023-06-17 22:15:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-17 22:15:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-17 22:15:05 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-17 22:15:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-17 22:15:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-17 22:15:05 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-17 22:15:05 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-17 22:15:05 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-17 22:15:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-17 22:15:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-17 22:15:05 (4119) [INFO] * 2023-06-17 22:15:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-17 22:15:05 (4089) [INFO] * 2023-06-17 22:15:29 (4102) [INFO] * 2023-06-17 22:15:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-17 22:15:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-17 22:15:29 (4119) [INFO] * 2023-06-17 22:15:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-17 22:15:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-17 22:15:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-17 22:15:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jicNsqV0LP/ea_profile.json * 2023-06-17 22:15:52 (2259) [INFO] Backed up EA4 profile to /tmp/jicNsqV0LP/ea_profile.json * 2023-06-17 22:15: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-06-17 22:15:53 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-18 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-18 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-18 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-06-18 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-18 22:15:07 (4089) [INFO] * 2023-06-18 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-18 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-18 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-18 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-18 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-18 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-18 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-18 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-18 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-18 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-18 22:15:07 (4119) [INFO] * 2023-06-18 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-18 22:15:07 (4089) [INFO] * 2023-06-18 22:15:32 (4102) [INFO] * 2023-06-18 22:15:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-18 22:15:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-18 22:15:32 (4119) [INFO] * 2023-06-18 22:15:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-18 22:15:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-18 22:15:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-18 22:15:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g_W9a4lnnO/ea_profile.json * 2023-06-18 22:15:56 (2259) [INFO] Backed up EA4 profile to /tmp/g_W9a4lnnO/ea_profile.json * 2023-06-18 22:15: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-18 22:15:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-19 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-19 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-19 22:14:09 (1700) [INFO] Checking if your system is up to date: * 2023-06-19 22:14:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-19 22:14:09 (4089) [INFO] * 2023-06-19 22:14:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-19 22:14:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-19 22:14:09 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-19 22:14:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-19 22:14:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-19 22:14:09 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-19 22:14:09 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-19 22:14:09 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-19 22:14:09 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-19 22:14:09 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-19 22:14:09 (4119) [INFO] * 2023-06-19 22:14:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-19 22:14:09 (4089) [INFO] * 2023-06-19 22:14:33 (4102) [INFO] * 2023-06-19 22:14:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-19 22:14:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-19 22:14:33 (4119) [INFO] * 2023-06-19 22:14:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-19 22:14:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-19 22:14:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-19 22:14:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tRKbMrbI79/ea_profile.json * 2023-06-19 22:14:57 (2259) [INFO] Backed up EA4 profile to /tmp/tRKbMrbI79/ea_profile.json * 2023-06-19 22:14: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-06-19 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-20 22:14:14 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-20 22:14:15 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-20 22:14:15 (1700) [INFO] Checking if your system is up to date: * 2023-06-20 22:14:15 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-20 22:14:15 (4089) [INFO] * 2023-06-20 22:14:15 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-20 22:14:15 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-20 22:14:15 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-20 22:14:15 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-20 22:14:15 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-20 22:14:15 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-20 22:14:15 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-20 22:14:15 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-20 22:14:15 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-20 22:14:15 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-20 22:14:15 (4119) [INFO] * 2023-06-20 22:14:15 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-20 22:14:15 (4089) [INFO] * 2023-06-20 22:14:39 (4102) [INFO] * 2023-06-20 22:14:39 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-20 22:14:39 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-20 22:14:39 (4119) [INFO] * 2023-06-20 22:14:39 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-20 22:14:39 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-20 22:15:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-20 22:15:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V2GhFqZ9cr/ea_profile.json * 2023-06-20 22:15:06 (2259) [INFO] Backed up EA4 profile to /tmp/V2GhFqZ9cr/ea_profile.json * 2023-06-20 22:15: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-06-20 22:15:07 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-21 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-21 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-21 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-21 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-21 22:14:06 (4089) [INFO] * 2023-06-21 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-21 22:14:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-21 22:14:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-21 22:14:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-21 22:14:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-21 22:14:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-21 22:14:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-21 22:14:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-21 22:14:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-21 22:14:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-21 22:14:07 (4119) [INFO] * 2023-06-21 22:14:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-21 22:14:07 (4089) [INFO] * 2023-06-21 22:14:30 (4102) [INFO] * 2023-06-21 22:14:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-21 22:14:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-21 22:14:30 (4119) [INFO] * 2023-06-21 22:14:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-21 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-21 22:14:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-21 22:14:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HgwzbEQUuc/ea_profile.json * 2023-06-21 22:14:56 (2259) [INFO] Backed up EA4 profile to /tmp/HgwzbEQUuc/ea_profile.json * 2023-06-21 22:14: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-21 22:14:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-22 22:14:23 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-22 22:14:23 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-22 22:14:23 (1700) [INFO] Checking if your system is up to date: * 2023-06-22 22:14:23 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-22 22:14:23 (4089) [INFO] * 2023-06-22 22:14:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-22 22:14:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-22 22:14:23 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-22 22:14:23 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-22 22:14:23 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-22 22:14:23 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-22 22:14:23 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-22 22:14:23 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-22 22:14:23 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-22 22:14:23 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-22 22:14:23 (4119) [INFO] * 2023-06-22 22:14:23 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-22 22:14:23 (4089) [INFO] * 2023-06-22 22:14:48 (4102) [INFO] * 2023-06-22 22:14:48 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-22 22:14:48 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-22 22:14:48 (4119) [INFO] * 2023-06-22 22:14:48 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-22 22:14:48 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-22 22:15:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-22 22:15:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sxDYUnwKIy/ea_profile.json * 2023-06-22 22:15:21 (2259) [INFO] Backed up EA4 profile to /tmp/sxDYUnwKIy/ea_profile.json * 2023-06-22 22:15: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-06-22 22:15:22 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-23 22:14:12 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-23 22:14:13 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-23 22:14:13 (1700) [INFO] Checking if your system is up to date: * 2023-06-23 22:14:13 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-23 22:14:13 (4089) [INFO] * 2023-06-23 22:14:13 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-23 22:14:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-23 22:14:13 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-23 22:14:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-23 22:14:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-23 22:14:13 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-23 22:14:13 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-23 22:14:13 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-23 22:14:13 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-23 22:14:13 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-23 22:14:13 (4119) [INFO] * 2023-06-23 22:14:13 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-23 22:14:13 (4089) [INFO] * 2023-06-23 22:14:37 (4102) [INFO] * 2023-06-23 22:14:37 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-23 22:14:37 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-23 22:14:37 (4119) [INFO] * 2023-06-23 22:14:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-23 22:14:37 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-23 22:15:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-23 22:15:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HTOC6Otm4R/ea_profile.json * 2023-06-23 22:15:00 (2259) [INFO] Backed up EA4 profile to /tmp/HTOC6Otm4R/ea_profile.json * 2023-06-23 22:15: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-23 22:15:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-24 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-24 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-24 22:15:09 (1700) [INFO] Checking if your system is up to date: * 2023-06-24 22:15:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-24 22:15:09 (4089) [INFO] * 2023-06-24 22:15:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-24 22:15:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-24 22:15:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-24 22:15:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-24 22:15:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-24 22:15:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-24 22:15:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-24 22:15:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-24 22:15:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-24 22:15:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-24 22:15:10 (4119) [INFO] * 2023-06-24 22:15:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-24 22:15:10 (4089) [INFO] * 2023-06-24 22:15:35 (4102) [INFO] * 2023-06-24 22:15:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-24 22:15:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-24 22:15:35 (4119) [INFO] * 2023-06-24 22:15:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-24 22:15:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-24 22:16:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-24 22:16:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DBcsAxAkmP/ea_profile.json * 2023-06-24 22:16:03 (2259) [INFO] Backed up EA4 profile to /tmp/DBcsAxAkmP/ea_profile.json * 2023-06-24 22:16:04 (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 22:16:04 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-25 22:15:00 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-25 22:15:01 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-25 22:15:01 (1700) [INFO] Checking if your system is up to date: * 2023-06-25 22:15:01 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-25 22:15:01 (4089) [INFO] * 2023-06-25 22:15:01 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-25 22:15:01 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-25 22:15:01 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-25 22:15:01 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-25 22:15:01 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-25 22:15:01 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-25 22:15:01 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-25 22:15:01 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-25 22:15:01 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-25 22:15:01 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-25 22:15:01 (4119) [INFO] * 2023-06-25 22:15:01 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-25 22:15:01 (4089) [INFO] * 2023-06-25 22:15:40 (4102) [INFO] * 2023-06-25 22:15:40 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-25 22:15:40 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-25 22:15:40 (4119) [INFO] * 2023-06-25 22:15:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-25 22:15:40 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-25 22:16:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-25 22:16:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PzweUaBPb7/ea_profile.json * 2023-06-25 22:16:07 (2259) [INFO] Backed up EA4 profile to /tmp/PzweUaBPb7/ea_profile.json * 2023-06-25 22:16:08 (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 22:16:08 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-26 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-26 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-26 22:14:10 (1700) [INFO] Checking if your system is up to date: * 2023-06-26 22:14:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-26 22:14:10 (4089) [INFO] * 2023-06-26 22:14:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-26 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-26 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-26 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-26 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-26 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-26 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-26 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-26 22:14:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-26 22:14:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-26 22:14:10 (4119) [INFO] * 2023-06-26 22:14:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-26 22:14:10 (4089) [INFO] * 2023-06-26 22:14:36 (4102) [INFO] * 2023-06-26 22:14:36 (4102) [INFO] kernel.x86_64 3.10.0-1160.90.1.el7 updates * 2023-06-26 22:14:36 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-26 22:14:36 (4119) [INFO] * 2023-06-26 22:14:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-26 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-26 22:14:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-26 22:14:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NzYDPNZW7i/ea_profile.json * 2023-06-26 22:14:59 (2259) [INFO] Backed up EA4 profile to /tmp/NzYDPNZW7i/ea_profile.json * 2023-06-26 22:15: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-06-26 22:15:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-27 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-27 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-27 22:14:36 (1700) [INFO] Checking if your system is up to date: * 2023-06-27 22:14:36 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-27 22:14:36 (4089) [INFO] * 2023-06-27 22:14:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-27 22:14:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-27 22:14:36 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-27 22:14:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-27 22:14:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-27 22:14:36 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-27 22:14:36 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-27 22:14:36 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-27 22:14:36 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-27 22:14:36 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-27 22:14:36 (4119) [INFO] * 2023-06-27 22:14:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-27 22:14:36 (4089) [INFO] * 2023-06-27 22:15:03 (4102) [INFO] * 2023-06-27 22:15:03 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-27 22:15:03 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-27 22:15:04 (4119) [INFO] * 2023-06-27 22:15:04 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-27 22:15:04 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-27 22:15:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-27 22:15:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2zFDYZSVxw/ea_profile.json * 2023-06-27 22:15:33 (2259) [INFO] Backed up EA4 profile to /tmp/2zFDYZSVxw/ea_profile.json * 2023-06-27 22:15: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-06-27 22:15:34 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-28 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-28 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-28 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-06-28 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-28 22:14:06 (4089) [INFO] * 2023-06-28 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-28 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-28 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-28 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-28 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-28 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-28 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-28 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-28 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-28 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-28 22:14:06 (4119) [INFO] * 2023-06-28 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-28 22:14:06 (4089) [INFO] * 2023-06-28 22:14:31 (4102) [INFO] * 2023-06-28 22:14:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-28 22:14:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-28 22:14:31 (4119) [INFO] * 2023-06-28 22:14:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-28 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-28 22:14:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-28 22:14:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KbIUfZMUr6/ea_profile.json * 2023-06-28 22:14:56 (2259) [INFO] Backed up EA4 profile to /tmp/KbIUfZMUr6/ea_profile.json * 2023-06-28 22:14: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-06-28 22:14:57 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-29 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-29 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-29 22:14:10 (1700) [INFO] Checking if your system is up to date: * 2023-06-29 22:14:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-29 22:14:10 (4089) [INFO] * 2023-06-29 22:14:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-29 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-29 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-29 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-29 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-29 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-29 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-29 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-29 22:14:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-29 22:14:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-29 22:14:10 (4119) [INFO] * 2023-06-29 22:14:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-29 22:14:10 (4089) [INFO] * 2023-06-29 22:14:37 (4102) [INFO] * 2023-06-29 22:14:37 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-29 22:14:37 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-29 22:14:37 (4119) [INFO] * 2023-06-29 22:14:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-29 22:14:37 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-29 22:15:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-29 22:15:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/py4aVfDpul/ea_profile.json * 2023-06-29 22:15:04 (2259) [INFO] Backed up EA4 profile to /tmp/py4aVfDpul/ea_profile.json * 2023-06-29 22:15:04 (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 22:15:04 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-06-30 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-06-30 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-06-30 22:14:05 (1700) [INFO] Checking if your system is up to date: * 2023-06-30 22:14:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-06-30 22:14:05 (4089) [INFO] * 2023-06-30 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-06-30 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-06-30 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-06-30 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-06-30 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-06-30 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-06-30 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-06-30 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-06-30 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-06-30 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-06-30 22:14:06 (4119) [INFO] * 2023-06-30 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-06-30 22:14:06 (4089) [INFO] * 2023-06-30 22:14:30 (4102) [INFO] * 2023-06-30 22:14:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-06-30 22:14:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-06-30 22:14:30 (4119) [INFO] * 2023-06-30 22:14:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-06-30 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-06-30 22:14:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-06-30 22:14:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GzMddT3vwK/ea_profile.json * 2023-06-30 22:14:54 (2259) [INFO] Backed up EA4 profile to /tmp/GzMddT3vwK/ea_profile.json * 2023-06-30 22:14: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-06-30 22:14:55 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-01 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-01 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-01 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-01 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-01 22:15:07 (4089) [INFO] * 2023-07-01 22:15:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-01 22:15:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-01 22:15:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-01 22:15:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-01 22:15:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-01 22:15:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-01 22:15:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-01 22:15:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-01 22:15:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-01 22:15:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-01 22:15:08 (4119) [INFO] * 2023-07-01 22:15:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-01 22:15:08 (4089) [INFO] * 2023-07-01 22:15:31 (4102) [INFO] * 2023-07-01 22:15:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-01 22:15:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-01 22:15:32 (4119) [INFO] * 2023-07-01 22:15:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-01 22:15:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-01 22:15:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-01 22:15:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xaBTEcXUBg/ea_profile.json * 2023-07-01 22:15:54 (2259) [INFO] Backed up EA4 profile to /tmp/xaBTEcXUBg/ea_profile.json * 2023-07-01 22:15: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-07-01 22:15:55 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-02 22:15:08 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-02 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-02 22:15:09 (1700) [INFO] Checking if your system is up to date: * 2023-07-02 22:15:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-02 22:15:09 (4089) [INFO] * 2023-07-02 22:15:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-02 22:15:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-02 22:15:09 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-02 22:15:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-02 22:15:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-02 22:15:09 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-02 22:15:09 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-02 22:15:09 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-02 22:15:09 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-02 22:15:09 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-02 22:15:09 (4119) [INFO] * 2023-07-02 22:15:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-02 22:15:09 (4089) [INFO] * 2023-07-02 22:15:34 (4102) [INFO] * 2023-07-02 22:15:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-02 22:15:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-02 22:15:34 (4119) [INFO] * 2023-07-02 22:15:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-02 22:15:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-02 22:16:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-02 22:16:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UpbVLDXz5Z/ea_profile.json * 2023-07-02 22:16:03 (2259) [INFO] Backed up EA4 profile to /tmp/UpbVLDXz5Z/ea_profile.json * 2023-07-02 22:16:04 (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 22:16:04 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-03 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-03 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-03 22:14:10 (1700) [INFO] Checking if your system is up to date: * 2023-07-03 22:14:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-03 22:14:10 (4089) [INFO] * 2023-07-03 22:14:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-03 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-03 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-03 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-03 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-03 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-03 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-03 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-03 22:14:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-03 22:14:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-03 22:14:11 (4119) [INFO] * 2023-07-03 22:14:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-03 22:14:11 (4089) [INFO] * 2023-07-03 22:14:36 (4102) [INFO] * 2023-07-03 22:14:36 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-03 22:14:36 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-03 22:14:36 (4119) [INFO] * 2023-07-03 22:14:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-03 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-03 22:14:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-03 22:14:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ERfobbkB8y/ea_profile.json * 2023-07-03 22:15:00 (2259) [INFO] Backed up EA4 profile to /tmp/ERfobbkB8y/ea_profile.json * 2023-07-03 22:15: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-07-03 22:15:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-04 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-04 22:14:11 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-04 22:14:11 (1700) [INFO] Checking if your system is up to date: * 2023-07-04 22:14:11 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-04 22:14:11 (4089) [INFO] * 2023-07-04 22:14:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-04 22:14:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-04 22:14:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-04 22:14:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-04 22:14:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-04 22:14:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-04 22:14:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-04 22:14:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-04 22:14:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-04 22:14:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-04 22:14:11 (4119) [INFO] * 2023-07-04 22:14:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-04 22:14:11 (4089) [INFO] * 2023-07-04 22:14:37 (4102) [INFO] * 2023-07-04 22:14:37 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-04 22:14:37 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-04 22:14:38 (4119) [INFO] * 2023-07-04 22:14:38 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-04 22:14:38 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-04 22:15:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-04 22:15:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1oeC9Wzhpq/ea_profile.json * 2023-07-04 22:15:02 (2259) [INFO] Backed up EA4 profile to /tmp/1oeC9Wzhpq/ea_profile.json * 2023-07-04 22:15:03 (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 22:15:03 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-05 22:14:11 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-05 22:14:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-05 22:14:12 (1700) [INFO] Checking if your system is up to date: * 2023-07-05 22:14:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-05 22:14:12 (4089) [INFO] * 2023-07-05 22:14:12 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-05 22:14:12 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-05 22:14:12 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-05 22:14:12 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-05 22:14:12 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-05 22:14:12 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-05 22:14:12 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-05 22:14:12 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-05 22:14:12 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-05 22:14:12 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-05 22:14:12 (4119) [INFO] * 2023-07-05 22:14:12 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-05 22:14:12 (4089) [INFO] * 2023-07-05 22:14:37 (4102) [INFO] * 2023-07-05 22:14:37 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-05 22:14:37 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-05 22:14:37 (4119) [INFO] * 2023-07-05 22:14:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-05 22:14:37 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-05 22:15:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-05 22:15:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nfxst6ABFQ/ea_profile.json * 2023-07-05 22:15:10 (2259) [INFO] Backed up EA4 profile to /tmp/nfxst6ABFQ/ea_profile.json * 2023-07-05 22:15: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-07-05 22:15:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-06 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-06 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-06 22:14:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-06 22:14:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-06 22:14:07 (4089) [INFO] * 2023-07-06 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-06 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-06 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-06 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-06 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-06 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-06 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-06 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-06 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-06 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-06 22:14:08 (4119) [INFO] * 2023-07-06 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-06 22:14:08 (4089) [INFO] * 2023-07-06 22:14:32 (4102) [INFO] * 2023-07-06 22:14:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-06 22:14:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-06 22:14:32 (4119) [INFO] * 2023-07-06 22:14:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-06 22:14:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-06 22:14:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-06 22:14:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tmVYurtmIZ/ea_profile.json * 2023-07-06 22:14:58 (2259) [INFO] Backed up EA4 profile to /tmp/tmVYurtmIZ/ea_profile.json * 2023-07-06 22:14: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-07-06 22:14:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-07 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-07 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-07 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-07-07 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-07 22:14:08 (4089) [INFO] * 2023-07-07 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-07 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-07 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-07 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-07 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-07 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-07 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-07 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-07 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-07 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-07 22:14:08 (4119) [INFO] * 2023-07-07 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-07 22:14:08 (4089) [INFO] * 2023-07-07 22:14:33 (4102) [INFO] * 2023-07-07 22:14:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-07 22:14:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-07 22:14:33 (4119) [INFO] * 2023-07-07 22:14:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-07 22:14:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-07 22:14:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-07 22:14:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tBmRA5MV0a/ea_profile.json * 2023-07-07 22:14:58 (2259) [INFO] Backed up EA4 profile to /tmp/tBmRA5MV0a/ea_profile.json * 2023-07-07 22:14: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-07-07 22:14:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-08 22:15:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-08 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-08 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-08 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-08 22:15:07 (4089) [INFO] * 2023-07-08 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-08 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-08 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-08 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-08 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-08 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-08 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-08 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-08 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-08 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-08 22:15:07 (4119) [INFO] * 2023-07-08 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-08 22:15:07 (4089) [INFO] * 2023-07-08 22:15:32 (4102) [INFO] * 2023-07-08 22:15:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-08 22:15:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-08 22:15:33 (4119) [INFO] * 2023-07-08 22:15:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-08 22:15:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-08 22:15:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-08 22:15:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IbfULKwh7j/ea_profile.json * 2023-07-08 22:15:56 (2259) [INFO] Backed up EA4 profile to /tmp/IbfULKwh7j/ea_profile.json * 2023-07-08 22:15: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-07-08 22:15:57 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-09 22:15:11 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-09 22:15:11 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-09 22:15:11 (1700) [INFO] Checking if your system is up to date: * 2023-07-09 22:15:11 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-09 22:15:11 (4089) [INFO] * 2023-07-09 22:15:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-09 22:15:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-09 22:15:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-09 22:15:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-09 22:15:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-09 22:15:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-09 22:15:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-09 22:15:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-09 22:15:12 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-09 22:15:12 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-09 22:15:12 (4119) [INFO] * 2023-07-09 22:15:12 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-09 22:15:12 (4089) [INFO] * 2023-07-09 22:15:44 (4102) [INFO] * 2023-07-09 22:15:44 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-09 22:15:44 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-09 22:15:44 (4119) [INFO] * 2023-07-09 22:15:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-09 22:15:44 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-09 22:16:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-09 22:16:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eRsgPJrfYn/ea_profile.json * 2023-07-09 22:16:08 (2259) [INFO] Backed up EA4 profile to /tmp/eRsgPJrfYn/ea_profile.json * 2023-07-09 22:16:09 (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 22:16:09 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-10 22:14:17 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-10 22:14:17 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-10 22:14:17 (1700) [INFO] Checking if your system is up to date: * 2023-07-10 22:14:17 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-10 22:14:17 (4089) [INFO] * 2023-07-10 22:14:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-10 22:14:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-10 22:14:18 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-10 22:14:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-10 22:14:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-10 22:14:18 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-10 22:14:18 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-10 22:14:18 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-10 22:14:18 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-10 22:14:18 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-10 22:14:18 (4119) [INFO] * 2023-07-10 22:14:18 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-10 22:14:18 (4089) [INFO] * 2023-07-10 22:14:43 (4102) [INFO] * 2023-07-10 22:14:43 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-10 22:14:43 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-10 22:14:43 (4119) [INFO] * 2023-07-10 22:14:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-10 22:14:43 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-10 22:15:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-10 22:15:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ogh4tLec6j/ea_profile.json * 2023-07-10 22:15:08 (2259) [INFO] Backed up EA4 profile to /tmp/Ogh4tLec6j/ea_profile.json * 2023-07-10 22:15:08 (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 22:15:08 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-11 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-11 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-11 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-07-11 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-11 22:14:08 (4089) [INFO] * 2023-07-11 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-11 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-11 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-11 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-11 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-11 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-11 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-11 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-11 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-11 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-11 22:14:08 (4119) [INFO] * 2023-07-11 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-11 22:14:08 (4089) [INFO] * 2023-07-11 22:14:34 (4102) [INFO] * 2023-07-11 22:14:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-11 22:14:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-11 22:14:34 (4119) [INFO] * 2023-07-11 22:14:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-11 22:14:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-11 22:14:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-11 22:14:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3gMugdEA4N/ea_profile.json * 2023-07-11 22:14:58 (2259) [INFO] Backed up EA4 profile to /tmp/3gMugdEA4N/ea_profile.json * 2023-07-11 22:14: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-07-11 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-12 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-12 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-12 22:14:10 (1700) [INFO] Checking if your system is up to date: * 2023-07-12 22:14:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-12 22:14:10 (4089) [INFO] * 2023-07-12 22:14:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-12 22:14:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-12 22:14:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-12 22:14:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-12 22:14:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-12 22:14:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-12 22:14:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-12 22:14:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-12 22:14:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-12 22:14:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-12 22:14:11 (4119) [INFO] * 2023-07-12 22:14:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-12 22:14:11 (4089) [INFO] * 2023-07-12 22:14:36 (4102) [INFO] * 2023-07-12 22:14:36 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-12 22:14:36 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-12 22:14:36 (4119) [INFO] * 2023-07-12 22:14:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-12 22:14:36 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-12 22:14:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-12 22:14:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0d20anV7KW/ea_profile.json * 2023-07-12 22:15:00 (2259) [INFO] Backed up EA4 profile to /tmp/0d20anV7KW/ea_profile.json * 2023-07-12 22:15: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-07-12 22:15:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-13 22:15:33 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-13 22:15:34 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-13 22:15:34 (1700) [INFO] Checking if your system is up to date: * 2023-07-13 22:15:34 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-13 22:15:34 (4089) [INFO] * 2023-07-13 22:15:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-13 22:15:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-13 22:15:34 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-13 22:15:34 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-13 22:15:34 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-13 22:15:34 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-13 22:15:34 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-13 22:15:34 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-13 22:15:34 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-13 22:15:34 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-13 22:15:34 (4119) [INFO] * 2023-07-13 22:15:34 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-13 22:15:34 (4089) [INFO] * 2023-07-13 22:15:59 (4102) [INFO] * 2023-07-13 22:15:59 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-13 22:15:59 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-13 22:15:59 (4119) [INFO] * 2023-07-13 22:15:59 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-13 22:15:59 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-13 22:16:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-13 22:16:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FGQRnSjenP/ea_profile.json * 2023-07-13 22:16:25 (2259) [INFO] Backed up EA4 profile to /tmp/FGQRnSjenP/ea_profile.json * 2023-07-13 22:16: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-07-13 22:16:26 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-14 22:14:55 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-14 22:14:56 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-14 22:14:56 (1700) [INFO] Checking if your system is up to date: * 2023-07-14 22:14:56 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-14 22:14:56 (4089) [INFO] * 2023-07-14 22:14:56 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-14 22:14:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-14 22:14:56 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-14 22:14:56 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-14 22:14:56 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-14 22:14:56 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-14 22:14:56 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-14 22:14:56 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-14 22:14:56 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-14 22:14:56 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-14 22:14:56 (4119) [INFO] * 2023-07-14 22:14:56 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-14 22:14:56 (4089) [INFO] * 2023-07-14 22:15:21 (4102) [INFO] * 2023-07-14 22:15:21 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-14 22:15:21 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-14 22:15:21 (4119) [INFO] * 2023-07-14 22:15:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-14 22:15:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-14 22:15:46 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-14 22:15:46 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e7rgtR0WoI/ea_profile.json * 2023-07-14 22:15:47 (2259) [INFO] Backed up EA4 profile to /tmp/e7rgtR0WoI/ea_profile.json * 2023-07-14 22:15: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-07-14 22:15:48 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-15 22:15:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-15 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-15 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-15 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-15 22:15:07 (4089) [INFO] * 2023-07-15 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-15 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-15 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-15 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-15 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-15 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-15 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-15 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-15 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-15 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-15 22:15:07 (4119) [INFO] * 2023-07-15 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-15 22:15:07 (4089) [INFO] * 2023-07-15 22:15:35 (4102) [INFO] * 2023-07-15 22:15:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-15 22:15:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-15 22:15:35 (4119) [INFO] * 2023-07-15 22:15:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-15 22:15:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-15 22:16:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-15 22:16:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AP7rsr4tFr/ea_profile.json * 2023-07-15 22:16:04 (2259) [INFO] Backed up EA4 profile to /tmp/AP7rsr4tFr/ea_profile.json * 2023-07-15 22:16: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-15 22:16:05 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-16 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-16 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-16 22:15:14 (1700) [INFO] Checking if your system is up to date: * 2023-07-16 22:15:14 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-16 22:15:14 (4089) [INFO] * 2023-07-16 22:15:14 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-16 22:15:15 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-16 22:15:15 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-16 22:15:15 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-16 22:15:15 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-16 22:15:15 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-16 22:15:15 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-16 22:15:15 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-16 22:15:15 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-16 22:15:15 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-16 22:15:15 (4119) [INFO] * 2023-07-16 22:15:15 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-16 22:15:15 (4089) [INFO] * 2023-07-16 22:15:40 (4102) [INFO] * 2023-07-16 22:15:40 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-16 22:15:40 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-16 22:15:41 (4119) [INFO] * 2023-07-16 22:15:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-16 22:15:41 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-16 22:16:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-16 22:16:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vz4F3iyOJy/ea_profile.json * 2023-07-16 22:16:07 (2259) [INFO] Backed up EA4 profile to /tmp/vz4F3iyOJy/ea_profile.json * 2023-07-16 22:16: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-07-16 22:16:07 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-17 22:16:10 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-17 22:16:11 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-17 22:16:11 (1700) [INFO] Checking if your system is up to date: * 2023-07-17 22:16:11 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-17 22:16:11 (4089) [INFO] * 2023-07-17 22:16:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-17 22:16:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-17 22:16:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-17 22:16:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-17 22:16:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-17 22:16:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-17 22:16:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-17 22:16:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-17 22:16:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-17 22:16:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-17 22:16:11 (4119) [INFO] * 2023-07-17 22:16:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-17 22:16:11 (4089) [INFO] * 2023-07-17 22:16:37 (4102) [INFO] * 2023-07-17 22:16:37 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-17 22:16:37 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-17 22:16:37 (4119) [INFO] * 2023-07-17 22:16:37 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-17 22:16:37 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-17 22:17:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-17 22:17:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ghHhJzY2XD/ea_profile.json * 2023-07-17 22:17:01 (2259) [INFO] Backed up EA4 profile to /tmp/ghHhJzY2XD/ea_profile.json * 2023-07-17 22:17: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-07-17 22:17:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-18 22:14:17 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-18 22:14:18 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-18 22:14:18 (1700) [INFO] Checking if your system is up to date: * 2023-07-18 22:14:18 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-18 22:14:18 (4089) [INFO] * 2023-07-18 22:14:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-18 22:14:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-18 22:14:18 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-18 22:14:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-18 22:14:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-18 22:14:18 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-18 22:14:18 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-18 22:14:18 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-18 22:14:18 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-18 22:14:18 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-18 22:14:18 (4119) [INFO] * 2023-07-18 22:14:18 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-18 22:14:18 (4089) [INFO] * 2023-07-18 22:14:41 (4102) [INFO] * 2023-07-18 22:14:41 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-18 22:14:41 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-18 22:14:42 (4119) [INFO] * 2023-07-18 22:14:42 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-18 22:14:42 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-18 22:15:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-18 22:15:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bKaQWqz5Ub/ea_profile.json * 2023-07-18 22:15:06 (2259) [INFO] Backed up EA4 profile to /tmp/bKaQWqz5Ub/ea_profile.json * 2023-07-18 22:15: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-07-18 22:15:07 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-19 22:15:36 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-19 22:15:36 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-19 22:15:36 (1700) [INFO] Checking if your system is up to date: * 2023-07-19 22:15:36 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-19 22:15:36 (4089) [INFO] * 2023-07-19 22:15:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-19 22:15:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-19 22:15:37 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-19 22:15:37 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-19 22:15:37 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-19 22:15:37 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-19 22:15:37 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-19 22:15:37 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-19 22:15:37 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-19 22:15:37 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-19 22:15:37 (4119) [INFO] * 2023-07-19 22:15:37 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-19 22:15:37 (4089) [INFO] * 2023-07-19 22:16:00 (4102) [INFO] * 2023-07-19 22:16:00 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-19 22:16:00 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-19 22:16:01 (4119) [INFO] * 2023-07-19 22:16:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-19 22:16:01 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-19 22:16:27 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-19 22:16:27 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gVZb0BDUpc/ea_profile.json * 2023-07-19 22:16:28 (2259) [INFO] Backed up EA4 profile to /tmp/gVZb0BDUpc/ea_profile.json * 2023-07-19 22:16: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-07-19 22:16:29 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-20 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-20 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-20 22:14:20 (1700) [INFO] Checking if your system is up to date: * 2023-07-20 22:14:20 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-20 22:14:20 (4089) [INFO] * 2023-07-20 22:14:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-20 22:14:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-20 22:14:21 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-20 22:14:21 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-20 22:14:21 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-20 22:14:21 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-20 22:14:21 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-20 22:14:21 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-20 22:14:21 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-20 22:14:21 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-20 22:14:21 (4119) [INFO] * 2023-07-20 22:14:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-20 22:14:21 (4089) [INFO] * 2023-07-20 22:14:46 (4102) [INFO] * 2023-07-20 22:14:46 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-20 22:14:46 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-20 22:14:46 (4119) [INFO] * 2023-07-20 22:14:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-20 22:14:46 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-20 22:15:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-20 22:15:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Mzhnwl1Jf6/ea_profile.json * 2023-07-20 22:15:10 (2259) [INFO] Backed up EA4 profile to /tmp/Mzhnwl1Jf6/ea_profile.json * 2023-07-20 22:15: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-07-20 22:15:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-21 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-21 22:14:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-21 22:14:10 (1700) [INFO] Checking if your system is up to date: * 2023-07-21 22:14:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-21 22:14:10 (4089) [INFO] * 2023-07-21 22:14:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-21 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-21 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-21 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-21 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-21 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-21 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-21 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-21 22:14:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-21 22:14:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-21 22:14:10 (4119) [INFO] * 2023-07-21 22:14:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-21 22:14:10 (4089) [INFO] * 2023-07-21 22:14:34 (4102) [INFO] * 2023-07-21 22:14:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-21 22:14:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-21 22:14:34 (4119) [INFO] * 2023-07-21 22:14:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-21 22:14:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-21 22:15:03 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-21 22:15:03 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qXQPlRr2rY/ea_profile.json * 2023-07-21 22:15:04 (2259) [INFO] Backed up EA4 profile to /tmp/qXQPlRr2rY/ea_profile.json * 2023-07-21 22:15:04 (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 22:15:04 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-22 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-22 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-22 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-22 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-22 22:15:07 (4089) [INFO] * 2023-07-22 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-22 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-22 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-22 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-22 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-22 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-22 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-22 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-22 22:15:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-22 22:15:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-22 22:15:08 (4119) [INFO] * 2023-07-22 22:15:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-22 22:15:08 (4089) [INFO] * 2023-07-22 22:15:33 (4102) [INFO] * 2023-07-22 22:15:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-22 22:15:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-22 22:15:34 (4119) [INFO] * 2023-07-22 22:15:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-22 22:15:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-22 22:15:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-22 22:15:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JUlDcLUxzC/ea_profile.json * 2023-07-22 22:15:58 (2259) [INFO] Backed up EA4 profile to /tmp/JUlDcLUxzC/ea_profile.json * 2023-07-22 22:15: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-07-22 22:15:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-23 22:15:03 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-23 22:15:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-23 22:15:04 (1700) [INFO] Checking if your system is up to date: * 2023-07-23 22:15:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-23 22:15:04 (4089) [INFO] * 2023-07-23 22:15:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-23 22:15:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-23 22:15:04 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-23 22:15:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-23 22:15:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-23 22:15:04 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-23 22:15:04 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-23 22:15:04 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-23 22:15:04 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-23 22:15:04 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-23 22:15:04 (4119) [INFO] * 2023-07-23 22:15:04 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-23 22:15:04 (4089) [INFO] * 2023-07-23 22:15:29 (4102) [INFO] * 2023-07-23 22:15:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-23 22:15:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-23 22:15:30 (4119) [INFO] * 2023-07-23 22:15:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-23 22:15:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-23 22:15:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-23 22:15:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_JYaj2JQ40/ea_profile.json * 2023-07-23 22:15:56 (2259) [INFO] Backed up EA4 profile to /tmp/_JYaj2JQ40/ea_profile.json * 2023-07-23 22:15: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-07-23 22:15:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-24 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-24 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-24 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-07-24 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-24 22:14:06 (4089) [INFO] * 2023-07-24 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-24 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-24 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-24 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-24 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-24 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-24 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-24 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-24 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-24 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-24 22:14:06 (4119) [INFO] * 2023-07-24 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-24 22:14:06 (4089) [INFO] * 2023-07-24 22:14:29 (4102) [INFO] * 2023-07-24 22:14:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-24 22:14:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-24 22:14:29 (4119) [INFO] * 2023-07-24 22:14:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-24 22:14:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-24 22:14:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-24 22:14:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gkixFAaqrq/ea_profile.json * 2023-07-24 22:14:56 (2259) [INFO] Backed up EA4 profile to /tmp/gkixFAaqrq/ea_profile.json * 2023-07-24 22:14: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-07-24 22:14:57 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-25 22:14:21 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-25 22:14:22 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-25 22:14:22 (1700) [INFO] Checking if your system is up to date: * 2023-07-25 22:14:22 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-25 22:14:22 (4089) [INFO] * 2023-07-25 22:14:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-25 22:14:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-25 22:14:22 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-25 22:14:22 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-25 22:14:22 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-25 22:14:22 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-25 22:14:22 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-25 22:14:22 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-25 22:14:22 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-25 22:14:22 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-25 22:14:22 (4119) [INFO] * 2023-07-25 22:14:22 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-25 22:14:22 (4089) [INFO] * 2023-07-25 22:14:46 (4102) [INFO] * 2023-07-25 22:14:46 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-25 22:14:46 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-25 22:14:46 (4119) [INFO] * 2023-07-25 22:14:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-25 22:14:46 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-25 22:15:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-25 22:15:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ixMgieNMkQ/ea_profile.json * 2023-07-25 22:15:11 (2259) [INFO] Backed up EA4 profile to /tmp/ixMgieNMkQ/ea_profile.json * 2023-07-25 22:15: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-07-25 22:15:12 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-26 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-26 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-26 22:14:07 (1700) [INFO] Checking if your system is up to date: * 2023-07-26 22:14:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-26 22:14:07 (4089) [INFO] * 2023-07-26 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-26 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-26 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-26 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-26 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-26 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-26 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-26 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-26 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-26 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-26 22:14:08 (4119) [INFO] * 2023-07-26 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-26 22:14:08 (4089) [INFO] * 2023-07-26 22:14:34 (4102) [INFO] * 2023-07-26 22:14:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-26 22:14:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-26 22:14:34 (4119) [INFO] * 2023-07-26 22:14:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-26 22:14:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-26 22:14:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-26 22:14:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5Vm9zw7IL4/ea_profile.json * 2023-07-26 22:14:59 (2259) [INFO] Backed up EA4 profile to /tmp/5Vm9zw7IL4/ea_profile.json * 2023-07-26 22:15: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-07-26 22:15:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-27 22:15:25 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-27 22:15:25 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-27 22:15:25 (1700) [INFO] Checking if your system is up to date: * 2023-07-27 22:15:25 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-27 22:15:25 (4089) [INFO] * 2023-07-27 22:15:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-27 22:15:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-27 22:15:26 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-27 22:15:26 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-27 22:15:26 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-27 22:15:26 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-27 22:15:26 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-27 22:15:26 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-27 22:15:26 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-27 22:15:26 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-27 22:15:26 (4119) [INFO] * 2023-07-27 22:15:26 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-27 22:15:26 (4089) [INFO] * 2023-07-27 22:15:50 (4102) [INFO] * 2023-07-27 22:15:50 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-27 22:15:50 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-27 22:15:50 (4119) [INFO] * 2023-07-27 22:15:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-27 22:15:50 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-27 22:16:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-27 22:16:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LTXjlcATHr/ea_profile.json * 2023-07-27 22:16:15 (2259) [INFO] Backed up EA4 profile to /tmp/LTXjlcATHr/ea_profile.json * 2023-07-27 22:16: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-07-27 22:16:15 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-28 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-28 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-28 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-07-28 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-28 22:14:06 (4089) [INFO] * 2023-07-28 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-28 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-28 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-28 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-28 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-28 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-28 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-28 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-28 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-28 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-28 22:14:06 (4119) [INFO] * 2023-07-28 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-28 22:14:06 (4089) [INFO] * 2023-07-28 22:14:29 (4102) [INFO] * 2023-07-28 22:14:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-28 22:14:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-28 22:14:29 (4119) [INFO] * 2023-07-28 22:14:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-28 22:14:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-28 22:14:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-28 22:14:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7bu5hU_S6z/ea_profile.json * 2023-07-28 22:14:54 (2259) [INFO] Backed up EA4 profile to /tmp/7bu5hU_S6z/ea_profile.json * 2023-07-28 22:14: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-07-28 22:14:55 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-29 22:15:17 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-29 22:15:17 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-29 22:15:17 (1700) [INFO] Checking if your system is up to date: * 2023-07-29 22:15:17 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-29 22:15:17 (4089) [INFO] * 2023-07-29 22:15:17 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-29 22:15:17 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-29 22:15:17 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-29 22:15:17 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-29 22:15:17 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-29 22:15:17 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-29 22:15:17 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-29 22:15:17 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-29 22:15:17 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-29 22:15:17 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-29 22:15:17 (4119) [INFO] * 2023-07-29 22:15:17 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-29 22:15:17 (4089) [INFO] * 2023-07-29 22:15:42 (4102) [INFO] * 2023-07-29 22:15:42 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-29 22:15:42 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-29 22:15:42 (4119) [INFO] * 2023-07-29 22:15:42 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-29 22:15:42 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-29 22:16:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-29 22:16:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_mpRfmg0Jv/ea_profile.json * 2023-07-29 22:16:07 (2259) [INFO] Backed up EA4 profile to /tmp/_mpRfmg0Jv/ea_profile.json * 2023-07-29 22:16: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-07-29 22:16:07 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-30 22:14:57 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-30 22:14:58 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-30 22:14:58 (1700) [INFO] Checking if your system is up to date: * 2023-07-30 22:14:58 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-30 22:14:58 (4089) [INFO] * 2023-07-30 22:14:58 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-30 22:14:58 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-30 22:14:58 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-30 22:14:58 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-30 22:14:58 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-30 22:14:58 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-30 22:14:58 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-30 22:14:58 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-30 22:14:58 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-30 22:14:58 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-30 22:14:58 (4119) [INFO] * 2023-07-30 22:14:58 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-30 22:14:58 (4089) [INFO] * 2023-07-30 22:15:24 (4102) [INFO] * 2023-07-30 22:15:24 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-30 22:15:24 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-30 22:15:24 (4119) [INFO] * 2023-07-30 22:15:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-30 22:15:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-30 22:15:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-30 22:15:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iGKhdMaORc/ea_profile.json * 2023-07-30 22:15:48 (2259) [INFO] Backed up EA4 profile to /tmp/iGKhdMaORc/ea_profile.json * 2023-07-30 22:15: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-07-30 22:15:48 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-07-31 22:14:59 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-07-31 22:15:00 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-07-31 22:15:00 (1700) [INFO] Checking if your system is up to date: * 2023-07-31 22:15:00 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-07-31 22:15:00 (4089) [INFO] * 2023-07-31 22:15:00 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-07-31 22:15:00 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-07-31 22:15:00 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-07-31 22:15:00 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-07-31 22:15:00 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-07-31 22:15:00 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-07-31 22:15:00 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-07-31 22:15:00 (4102) [INFO] : wp-toolkit-thirdparties * 2023-07-31 22:15:00 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-07-31 22:15:00 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-07-31 22:15:00 (4119) [INFO] * 2023-07-31 22:15:00 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-07-31 22:15:00 (4089) [INFO] * 2023-07-31 22:15:26 (4102) [INFO] * 2023-07-31 22:15:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-07-31 22:15:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-07-31 22:15:26 (4119) [INFO] * 2023-07-31 22:15:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-07-31 22:15:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-07-31 22:15:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-07-31 22:15:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kk4EMswfbO/ea_profile.json * 2023-07-31 22:15:51 (2259) [INFO] Backed up EA4 profile to /tmp/Kk4EMswfbO/ea_profile.json * 2023-07-31 22:15: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-31 22:15:52 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-01 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-01 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-01 22:14:09 (1700) [INFO] Checking if your system is up to date: * 2023-08-01 22:14:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-01 22:14:09 (4089) [INFO] * 2023-08-01 22:14:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-01 22:14:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-01 22:14:10 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-01 22:14:10 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-01 22:14:10 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-01 22:14:10 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-01 22:14:10 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-01 22:14:10 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-01 22:14:10 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-01 22:14:10 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-01 22:14:10 (4119) [INFO] * 2023-08-01 22:14:10 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-01 22:14:10 (4089) [INFO] * 2023-08-01 22:14:34 (4102) [INFO] * 2023-08-01 22:14:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-08-01 22:14:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-01 22:14:34 (4119) [INFO] * 2023-08-01 22:14:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-01 22:14:34 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-01 22:14:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-01 22:14:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/isWp1GFlZY/ea_profile.json * 2023-08-01 22:14:59 (2259) [INFO] Backed up EA4 profile to /tmp/isWp1GFlZY/ea_profile.json * 2023-08-01 22:15: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-01 22:15:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-02 22:15:52 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-02 22:15:53 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-02 22:15:53 (1700) [INFO] Checking if your system is up to date: * 2023-08-02 22:15:53 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-02 22:15:53 (4089) [INFO] * 2023-08-02 22:15:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-02 22:15:53 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-02 22:15:53 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-02 22:15:53 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-02 22:15:53 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-02 22:15:53 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-02 22:15:53 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-02 22:15:53 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-02 22:15:53 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-02 22:15:53 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-02 22:15:53 (4119) [INFO] * 2023-08-02 22:15:53 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-02 22:15:53 (4089) [INFO] * 2023-08-02 22:16:18 (4102) [INFO] * 2023-08-02 22:16:18 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-08-02 22:16:18 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-02 22:16:18 (4119) [INFO] * 2023-08-02 22:16:18 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-02 22:16:18 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-02 22:16:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-02 22:16:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NInzEmY075/ea_profile.json * 2023-08-02 22:16:42 (2259) [INFO] Backed up EA4 profile to /tmp/NInzEmY075/ea_profile.json * 2023-08-02 22:16: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-02 22:16:43 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-03 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-03 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-03 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-08-03 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-03 22:14:08 (4089) [INFO] * 2023-08-03 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-03 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-03 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-03 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-03 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-03 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-03 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-03 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-03 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-03 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-03 22:14:08 (4119) [INFO] * 2023-08-03 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-03 22:14:08 (4089) [INFO] * 2023-08-03 22:14:31 (4102) [INFO] * 2023-08-03 22:14:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.92.1.el7 updates * 2023-08-03 22:14:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-03 22:14:31 (4119) [INFO] * 2023-08-03 22:14:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-03 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-03 22:14:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-03 22:14:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/haEKkxsRSG/ea_profile.json * 2023-08-03 22:14:55 (2259) [INFO] Backed up EA4 profile to /tmp/haEKkxsRSG/ea_profile.json * 2023-08-03 22:14: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-08-03 22:14:56 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-04 22:14:28 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-04 22:14:29 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-04 22:14:29 (1700) [INFO] Checking if your system is up to date: * 2023-08-04 22:14:29 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-04 22:14:29 (4089) [INFO] * 2023-08-04 22:14:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-04 22:14:30 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-04 22:14:30 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-04 22:14:30 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-04 22:14:30 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-04 22:14:30 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-04 22:14:30 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-04 22:14:30 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-04 22:14:30 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-04 22:14:30 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-04 22:14:30 (4119) [INFO] * 2023-08-04 22:14:30 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-04 22:14:30 (4089) [INFO] * 2023-08-04 22:14:54 (4102) [INFO] * 2023-08-04 22:14:54 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-04 22:14:54 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-04 22:14:55 (4119) [INFO] * 2023-08-04 22:14:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-04 22:14:55 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-04 22:15:20 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-04 22:15:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9814jXn20P/ea_profile.json * 2023-08-04 22:15:21 (2259) [INFO] Backed up EA4 profile to /tmp/9814jXn20P/ea_profile.json * 2023-08-04 22:15: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-04 22:15:22 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-05 22:15:21 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-05 22:15:22 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-05 22:15:22 (1700) [INFO] Checking if your system is up to date: * 2023-08-05 22:15:22 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-05 22:15:22 (4089) [INFO] * 2023-08-05 22:15:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-05 22:15:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-05 22:15:22 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-05 22:15:22 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-05 22:15:22 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-05 22:15:22 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-05 22:15:22 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-05 22:15:22 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-05 22:15:22 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-05 22:15:22 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-05 22:15:22 (4119) [INFO] * 2023-08-05 22:15:22 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-05 22:15:22 (4089) [INFO] * 2023-08-05 22:15:49 (4102) [INFO] * 2023-08-05 22:15:49 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-05 22:15:49 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-05 22:15:50 (4119) [INFO] * 2023-08-05 22:15:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-05 22:15:50 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-05 22:16:15 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-05 22:16:15 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WRPZrAPkUk/ea_profile.json * 2023-08-05 22:16:16 (2259) [INFO] Backed up EA4 profile to /tmp/WRPZrAPkUk/ea_profile.json * 2023-08-05 22:16:17 (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 22:16:17 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-06 22:15:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-06 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-06 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-08-06 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-06 22:15:07 (4089) [INFO] * 2023-08-06 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-06 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-06 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-06 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-06 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-06 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-06 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-06 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-06 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-06 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-06 22:15:07 (4119) [INFO] * 2023-08-06 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-06 22:15:07 (4089) [INFO] * 2023-08-06 22:15:33 (4102) [INFO] * 2023-08-06 22:15:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-06 22:15:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-06 22:15:33 (4119) [INFO] * 2023-08-06 22:15:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-06 22:15:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-06 22:15:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-06 22:15:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MWm3qpBeuc/ea_profile.json * 2023-08-06 22:15:59 (2259) [INFO] Backed up EA4 profile to /tmp/MWm3qpBeuc/ea_profile.json * 2023-08-06 22:16: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-06 22:16:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-07 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-07 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-07 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-08-07 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-07 22:14:08 (4089) [INFO] * 2023-08-07 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-07 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-07 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-07 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-07 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-07 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-07 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-07 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-07 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-07 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-07 22:14:08 (4119) [INFO] * 2023-08-07 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-07 22:14:08 (4089) [INFO] * 2023-08-07 22:14:32 (4102) [INFO] * 2023-08-07 22:14:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-07 22:14:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-07 22:14:32 (4119) [INFO] * 2023-08-07 22:14:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-07 22:14:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-07 22:14:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-07 22:14:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aeutxqcMBA/ea_profile.json * 2023-08-07 22:14:57 (2259) [INFO] Backed up EA4 profile to /tmp/aeutxqcMBA/ea_profile.json * 2023-08-07 22:14: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-07 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-08 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-08 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-08 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-08-08 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-08 22:14:06 (4089) [INFO] * 2023-08-08 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-08 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-08 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-08 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-08 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-08 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-08 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-08 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-08 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-08 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-08 22:14:06 (4119) [INFO] * 2023-08-08 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-08 22:14:06 (4089) [INFO] * 2023-08-08 22:14:27 (4102) [INFO] * 2023-08-08 22:14:27 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-08 22:14:27 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-08 22:14:27 (4119) [INFO] * 2023-08-08 22:14:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-08 22:14:27 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-08 22:14:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-08 22:14:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vYpywFqB4n/ea_profile.json * 2023-08-08 22:14:52 (2259) [INFO] Backed up EA4 profile to /tmp/vYpywFqB4n/ea_profile.json * 2023-08-08 22:14: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-08 22:14:53 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-09 22:15:48 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-09 22:15:48 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-09 22:15:48 (1700) [INFO] Checking if your system is up to date: * 2023-08-09 22:15:48 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-09 22:15:48 (4089) [INFO] * 2023-08-09 22:15:49 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-09 22:15:49 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-09 22:15:49 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-09 22:15:49 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-09 22:15:49 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-09 22:15:49 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-09 22:15:49 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-09 22:15:49 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-09 22:15:49 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-09 22:15:49 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-09 22:15:49 (4119) [INFO] * 2023-08-09 22:15:49 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-09 22:15:49 (4089) [INFO] * 2023-08-09 22:16:13 (4102) [INFO] * 2023-08-09 22:16:13 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-09 22:16:13 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-09 22:16:13 (4119) [INFO] * 2023-08-09 22:16:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-09 22:16:13 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-09 22:16:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-09 22:16:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sw0XOfzDtl/ea_profile.json * 2023-08-09 22:16:38 (2259) [INFO] Backed up EA4 profile to /tmp/sw0XOfzDtl/ea_profile.json * 2023-08-09 22:16: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-08-09 22:16:38 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-10 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-10 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-10 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-08-10 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-10 22:14:06 (4089) [INFO] * 2023-08-10 22:14:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-10 22:14:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-10 22:14:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-10 22:14:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-10 22:14:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-10 22:14:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-10 22:14:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-10 22:14:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-10 22:14:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-10 22:14:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-10 22:14:07 (4119) [INFO] * 2023-08-10 22:14:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-10 22:14:07 (4089) [INFO] * 2023-08-10 22:14:33 (4102) [INFO] * 2023-08-10 22:14:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-10 22:14:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-10 22:14:33 (4119) [INFO] * 2023-08-10 22:14:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-10 22:14:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-10 22:15:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-10 22:15:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wwiQrWQLhj/ea_profile.json * 2023-08-10 22:15:01 (2259) [INFO] Backed up EA4 profile to /tmp/wwiQrWQLhj/ea_profile.json * 2023-08-10 22:15:03 (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 22:15:03 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-11 22:14:12 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-11 22:14:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-11 22:14:12 (1700) [INFO] Checking if your system is up to date: * 2023-08-11 22:14:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-11 22:14:12 (4089) [INFO] * 2023-08-11 22:14:12 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-11 22:14:13 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-11 22:14:13 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-11 22:14:13 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-11 22:14:13 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-11 22:14:13 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-11 22:14:13 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-11 22:14:13 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-11 22:14:13 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-11 22:14:13 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-11 22:14:13 (4119) [INFO] * 2023-08-11 22:14:13 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-11 22:14:13 (4089) [INFO] * 2023-08-11 22:14:34 (4102) [INFO] * 2023-08-11 22:14:34 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-11 22:14:34 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-11 22:14:35 (4119) [INFO] * 2023-08-11 22:14:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-11 22:14:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-11 22:15:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-11 22:15:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bm3GHx3CEq/ea_profile.json * 2023-08-11 22:15:08 (2259) [INFO] Backed up EA4 profile to /tmp/bm3GHx3CEq/ea_profile.json * 2023-08-11 22:15: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-08-11 22:15:12 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-12 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-12 22:15:14 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-12 22:15:14 (1700) [INFO] Checking if your system is up to date: * 2023-08-12 22:15:14 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-12 22:15:14 (4089) [INFO] * 2023-08-12 22:15:15 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-12 22:15:15 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-12 22:15:15 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-12 22:15:15 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-12 22:15:15 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-12 22:15:15 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-12 22:15:15 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-12 22:15:15 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-12 22:15:15 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-12 22:15:15 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-12 22:15:15 (4119) [INFO] * 2023-08-12 22:15:15 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-12 22:15:15 (4089) [INFO] * 2023-08-12 22:15:40 (4102) [INFO] * 2023-08-12 22:15:40 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-12 22:15:40 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-12 22:15:40 (4119) [INFO] * 2023-08-12 22:15:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-12 22:15:40 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-12 22:16:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-12 22:16:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I_44AeSOOK/ea_profile.json * 2023-08-12 22:16:08 (2259) [INFO] Backed up EA4 profile to /tmp/I_44AeSOOK/ea_profile.json * 2023-08-12 22:16:09 (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 22:16:09 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-13 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-13 22:15:10 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-13 22:15:10 (1700) [INFO] Checking if your system is up to date: * 2023-08-13 22:15:10 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-13 22:15:10 (4089) [INFO] * 2023-08-13 22:15:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-13 22:15:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-13 22:15:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-13 22:15:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-13 22:15:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-13 22:15:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-13 22:15:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-13 22:15:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-13 22:15:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-13 22:15:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-13 22:15:11 (4119) [INFO] * 2023-08-13 22:15:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-13 22:15:11 (4089) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] Could not retrieve mirrorlist http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist error was * 2023-08-13 22:15:43 (4102) [INFO] 12: Timeout on http://httpupdate.cpanel.net/cPAddons-c7-x86_64-mirrorlist: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] One of the configured repositories failed (Unknown), * 2023-08-13 22:15:43 (4102) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-08-13 22:15:43 (4102) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-08-13 22:15:43 (4102) [INFO] upstream. This is most often useful if you are using a newer * 2023-08-13 22:15:43 (4102) [INFO] distribution release than is supported by the repository (and the * 2023-08-13 22:15:43 (4102) [INFO] packages for the previous distribution release still work). * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] 3. Run the command with the repository temporarily disabled * 2023-08-13 22:15:43 (4102) [INFO] yum --disablerepo= ... * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-08-13 22:15:43 (4102) [INFO] will then just ignore the repository until you permanently enable it * 2023-08-13 22:15:43 (4102) [INFO] again or use --enablerepo for temporary usage: * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] yum-config-manager --disable * 2023-08-13 22:15:43 (4102) [INFO] or * 2023-08-13 22:15:43 (4102) [INFO] subscription-manager repos --disable= * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-08-13 22:15:43 (4102) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-08-13 22:15:43 (4102) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-08-13 22:15:43 (4102) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-08-13 22:15:43 (4102) [INFO] compromise: * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-08-13 22:15:43 (4102) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] Cannot find a valid baseurl for repo: cpanel-addons-production-feed/x86_64 * 2023-08-13 22:15:43 (4119) [INFO] * 2023-08-13 22:15:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-13 22:15:43 (1721) [INFO] Checking /scripts/sysup * 2023-08-13 22:15:43 (4088) [INFO] Running: /scripts/sysup * 2023-08-13 22:15:43 (4089) [INFO] * 2023-08-13 22:15:43 (4102) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-08-13 22:15:44 (4102) [INFO] All Needed Packages are already installed. * 2023-08-13 22:15:44 (4119) [INFO] * 2023-08-13 22:16:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-13 22:16:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9UbHp2vahH/ea_profile.json * 2023-08-13 22:16:30 (2259) [INFO] Backed up EA4 profile to /tmp/9UbHp2vahH/ea_profile.json * 2023-08-13 22:16: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-08-13 22:16:31 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-14 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-14 22:14:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-14 22:14:09 (1700) [INFO] Checking if your system is up to date: * 2023-08-14 22:14:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-14 22:14:09 (4089) [INFO] * 2023-08-14 22:14:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-14 22:14:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-14 22:14:09 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-14 22:14:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-14 22:14:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-14 22:14:09 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-14 22:14:09 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-14 22:14:09 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-14 22:14:09 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-14 22:14:09 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-14 22:14:09 (4119) [INFO] * 2023-08-14 22:14:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-14 22:14:09 (4089) [INFO] * 2023-08-14 22:14:32 (4102) [INFO] * 2023-08-14 22:14:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-14 22:14:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-14 22:14:32 (4119) [INFO] * 2023-08-14 22:14:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-14 22:14:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-14 22:14:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-14 22:14:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sNes5V3u6S/ea_profile.json * 2023-08-14 22:14:57 (2259) [INFO] Backed up EA4 profile to /tmp/sNes5V3u6S/ea_profile.json * 2023-08-14 22:14: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-14 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-15 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-15 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-15 22:14:20 (1700) [INFO] Checking if your system is up to date: * 2023-08-15 22:14:20 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-15 22:14:20 (4089) [INFO] * 2023-08-15 22:14:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-15 22:14:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-15 22:14:21 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-15 22:14:21 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-15 22:14:21 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-15 22:14:21 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-15 22:14:21 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-15 22:14:21 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-15 22:14:21 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-15 22:14:21 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-15 22:14:21 (4119) [INFO] * 2023-08-15 22:14:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-15 22:14:21 (4089) [INFO] * 2023-08-15 22:14:43 (4102) [INFO] * 2023-08-15 22:14:43 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-15 22:14:43 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-15 22:14:43 (4119) [INFO] * 2023-08-15 22:14:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-15 22:14:43 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-15 22:15:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-15 22:15:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xApKFvaSnK/ea_profile.json * 2023-08-15 22:15:16 (2259) [INFO] Backed up EA4 profile to /tmp/xApKFvaSnK/ea_profile.json * 2023-08-15 22:15: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-08-15 22:15:16 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-16 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-16 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-16 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-08-16 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-16 22:14:08 (4089) [INFO] * 2023-08-16 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-16 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-16 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-16 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-16 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-16 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-16 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-16 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-16 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-16 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-16 22:14:08 (4119) [INFO] * 2023-08-16 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-16 22:14:08 (4089) [INFO] * 2023-08-16 22:14:31 (4102) [INFO] * 2023-08-16 22:14:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-16 22:14:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-16 22:14:31 (4119) [INFO] * 2023-08-16 22:14:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-16 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-16 22:14:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-16 22:14:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nJXrWLXf21/ea_profile.json * 2023-08-16 22:14:58 (2259) [INFO] Backed up EA4 profile to /tmp/nJXrWLXf21/ea_profile.json * 2023-08-16 22:14: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-16 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-17 22:15:28 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-17 22:15:28 (1700) [INFO] Checking if your system is up to date: * 2023-08-17 22:15:28 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-17 22:15:28 (4089) [INFO] * 2023-08-17 22:15:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-17 22:15:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-17 22:15:28 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-17 22:15:28 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-17 22:15:28 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-17 22:15:28 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-17 22:15:28 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-17 22:15:28 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-17 22:15:28 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-17 22:15:28 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-17 22:15:28 (4119) [INFO] * 2023-08-17 22:15:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-17 22:15:28 (4089) [INFO] * 2023-08-17 22:15:53 (4102) [INFO] * 2023-08-17 22:15:53 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-17 22:15:53 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-17 22:15:53 (4119) [INFO] * 2023-08-17 22:15:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-17 22:15:53 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-17 22:16:18 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-17 22:16:18 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vswc3tX1N8/ea_profile.json * 2023-08-17 22:16:18 (2259) [INFO] Backed up EA4 profile to /tmp/vswc3tX1N8/ea_profile.json * 2023-08-17 22:16: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-08-17 22:16:19 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-18 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-18 22:14:04 (1700) [INFO] Checking if your system is up to date: * 2023-08-18 22:14:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-18 22:14:04 (4089) [INFO] * 2023-08-18 22:14:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-18 22:14:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-18 22:14:04 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-18 22:14:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-18 22:14:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-18 22:14:04 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-18 22:14:04 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-18 22:14:04 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-18 22:14:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-18 22:14:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-18 22:14:05 (4119) [INFO] * 2023-08-18 22:14:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-18 22:14:05 (4089) [INFO] * 2023-08-18 22:14:27 (4102) [INFO] * 2023-08-18 22:14:27 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-18 22:14:27 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-18 22:14:27 (4119) [INFO] * 2023-08-18 22:14:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-18 22:14:27 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-18 22:14:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-18 22:14:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XTKJrjuA4O/ea_profile.json * 2023-08-18 22:14:54 (2259) [INFO] Backed up EA4 profile to /tmp/XTKJrjuA4O/ea_profile.json * 2023-08-18 22:14: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-08-18 22:14:54 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-19 22:15:18 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-19 22:15:18 (1700) [INFO] Checking if your system is up to date: * 2023-08-19 22:15:18 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-19 22:15:18 (4089) [INFO] * 2023-08-19 22:15:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-19 22:15:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-19 22:15:18 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-19 22:15:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-19 22:15:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-19 22:15:18 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-19 22:15:18 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-19 22:15:18 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-19 22:15:19 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-19 22:15:19 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-19 22:15:19 (4119) [INFO] * 2023-08-19 22:15:19 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-19 22:15:19 (4089) [INFO] * 2023-08-19 22:16:05 (4102) [INFO] * 2023-08-19 22:16:05 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-19 22:16:05 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-19 22:16:06 (4119) [INFO] * 2023-08-19 22:16:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-19 22:16:06 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-19 22:16:30 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-19 22:16:30 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lUe9HbXBC9/ea_profile.json * 2023-08-19 22:16:31 (2259) [INFO] Backed up EA4 profile to /tmp/lUe9HbXBC9/ea_profile.json * 2023-08-19 22:16: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-08-19 22:16:31 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-20 22:15:03 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-20 22:15:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-20 22:15:04 (1700) [INFO] Checking if your system is up to date: * 2023-08-20 22:15:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-20 22:15:04 (4089) [INFO] * 2023-08-20 22:15:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-20 22:15:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-20 22:15:05 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-20 22:15:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-20 22:15:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-20 22:15:05 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-20 22:15:05 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-20 22:15:05 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-20 22:15:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-20 22:15:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-20 22:15:05 (4119) [INFO] * 2023-08-20 22:15:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-20 22:15:05 (4089) [INFO] * 2023-08-20 22:15:30 (4102) [INFO] * 2023-08-20 22:15:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-20 22:15:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-20 22:15:30 (4119) [INFO] * 2023-08-20 22:15:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-20 22:15:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-20 22:16:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-20 22:16:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pmSuvHIoBY/ea_profile.json * 2023-08-20 22:16:01 (2259) [INFO] Backed up EA4 profile to /tmp/pmSuvHIoBY/ea_profile.json * 2023-08-20 22:16: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-20 22:16:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-21 22:14:11 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-21 22:14:12 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-21 22:14:12 (1700) [INFO] Checking if your system is up to date: * 2023-08-21 22:14:12 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-21 22:14:12 (4089) [INFO] * 2023-08-21 22:14:12 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-21 22:14:12 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-21 22:14:12 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-21 22:14:12 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-21 22:14:12 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-21 22:14:12 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-21 22:14:12 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-21 22:14:12 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-21 22:14:12 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-21 22:14:12 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-21 22:14:12 (4119) [INFO] * 2023-08-21 22:14:12 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-21 22:14:12 (4089) [INFO] * 2023-08-21 22:14:35 (4102) [INFO] * 2023-08-21 22:14:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-21 22:14:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-21 22:14:35 (4119) [INFO] * 2023-08-21 22:14:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-21 22:14:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-21 22:15:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-21 22:15:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lalJ3K4RLl/ea_profile.json * 2023-08-21 22:15:03 (2259) [INFO] Backed up EA4 profile to /tmp/lalJ3K4RLl/ea_profile.json * 2023-08-21 22:15:03 (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 22:15:03 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-22 22:15:51 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-22 22:15:52 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-22 22:15:52 (1700) [INFO] Checking if your system is up to date: * 2023-08-22 22:15:52 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-22 22:15:52 (4089) [INFO] * 2023-08-22 22:15:52 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-22 22:15:52 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-22 22:15:52 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-22 22:15:52 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-22 22:15:52 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-22 22:15:52 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-22 22:15:52 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-22 22:15:52 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-22 22:15:52 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-22 22:15:52 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-22 22:15:52 (4119) [INFO] * 2023-08-22 22:15:52 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-22 22:15:52 (4089) [INFO] * 2023-08-22 22:16:18 (4102) [INFO] * 2023-08-22 22:16:18 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-22 22:16:18 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-22 22:16:18 (4119) [INFO] * 2023-08-22 22:16:18 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-22 22:16:18 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-22 22:16:43 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-22 22:16:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4nEbw99M7I/ea_profile.json * 2023-08-22 22:16:45 (2259) [INFO] Backed up EA4 profile to /tmp/4nEbw99M7I/ea_profile.json * 2023-08-22 22:16: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-22 22:16:46 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-23 22:14:16 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-23 22:14:16 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-23 22:14:16 (1700) [INFO] Checking if your system is up to date: * 2023-08-23 22:14:16 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-23 22:14:16 (4089) [INFO] * 2023-08-23 22:14:16 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-23 22:14:16 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-23 22:14:16 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-23 22:14:16 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-23 22:14:16 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-23 22:14:16 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-23 22:14:16 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-23 22:14:16 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-23 22:14:16 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-23 22:14:16 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-23 22:14:17 (4119) [INFO] * 2023-08-23 22:14:17 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-23 22:14:17 (4089) [INFO] * 2023-08-23 22:14:39 (4102) [INFO] * 2023-08-23 22:14:39 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-23 22:14:39 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-23 22:14:39 (4119) [INFO] * 2023-08-23 22:14:39 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-23 22:14:39 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-23 22:15:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-23 22:15:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cbOJNsbX30/ea_profile.json * 2023-08-23 22:15:05 (2259) [INFO] Backed up EA4 profile to /tmp/cbOJNsbX30/ea_profile.json * 2023-08-23 22:15: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-23 22:15:06 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-24 22:14:27 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-24 22:14:28 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-24 22:14:28 (1700) [INFO] Checking if your system is up to date: * 2023-08-24 22:14:28 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-24 22:14:28 (4089) [INFO] * 2023-08-24 22:14:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-24 22:14:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-24 22:14:28 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-24 22:14:28 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-24 22:14:28 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-24 22:14:28 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-24 22:14:28 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-24 22:14:28 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-24 22:14:28 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-24 22:14:28 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-24 22:14:28 (4119) [INFO] * 2023-08-24 22:14:28 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-24 22:14:28 (4089) [INFO] * 2023-08-24 22:14:50 (4102) [INFO] * 2023-08-24 22:14:50 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-24 22:14:50 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-24 22:14:50 (4119) [INFO] * 2023-08-24 22:14:50 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-24 22:14:50 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-24 22:15:18 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-24 22:15:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dkuNdHLCqq/ea_profile.json * 2023-08-24 22:15:19 (2259) [INFO] Backed up EA4 profile to /tmp/dkuNdHLCqq/ea_profile.json * 2023-08-24 22:15: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-24 22:15:20 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-25 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-25 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-25 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-08-25 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-25 22:14:08 (4089) [INFO] * 2023-08-25 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-25 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-25 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-25 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-25 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-25 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-25 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-25 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-25 22:14:09 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-25 22:14:09 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-25 22:14:09 (4119) [INFO] * 2023-08-25 22:14:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-25 22:14:09 (4089) [INFO] * 2023-08-25 22:14:31 (4102) [INFO] * 2023-08-25 22:14:31 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-25 22:14:31 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-25 22:14:31 (4119) [INFO] * 2023-08-25 22:14:31 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-25 22:14:31 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-25 22:14:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-25 22:14:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XbJ4fQ3k24/ea_profile.json * 2023-08-25 22:14:57 (2259) [INFO] Backed up EA4 profile to /tmp/XbJ4fQ3k24/ea_profile.json * 2023-08-25 22:14: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-25 22:14:58 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-26 22:16:10 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-26 22:16:11 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-26 22:16:11 (1700) [INFO] Checking if your system is up to date: * 2023-08-26 22:16:11 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-26 22:16:11 (4089) [INFO] * 2023-08-26 22:16:11 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-26 22:16:11 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-26 22:16:11 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-26 22:16:11 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-26 22:16:11 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-26 22:16:11 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-26 22:16:11 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-26 22:16:11 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-26 22:16:11 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-26 22:16:11 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-26 22:16:11 (4119) [INFO] * 2023-08-26 22:16:11 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-26 22:16:11 (4089) [INFO] * 2023-08-26 22:16:35 (4102) [INFO] * 2023-08-26 22:16:35 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-26 22:16:35 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-26 22:16:35 (4119) [INFO] * 2023-08-26 22:16:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-26 22:16:35 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-26 22:17:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-26 22:17:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XxjPtv5Dz1/ea_profile.json * 2023-08-26 22:17:01 (2259) [INFO] Backed up EA4 profile to /tmp/XxjPtv5Dz1/ea_profile.json * 2023-08-26 22:17: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-26 22:17:02 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-27 22:15:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-27 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-27 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-08-27 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-27 22:15:07 (4089) [INFO] * 2023-08-27 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-27 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-27 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-27 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-27 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-27 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-27 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-27 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-27 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-27 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-27 22:15:07 (4119) [INFO] * 2023-08-27 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-27 22:15:07 (4089) [INFO] * 2023-08-27 22:15:32 (4102) [INFO] * 2023-08-27 22:15:32 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-27 22:15:32 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-27 22:15:32 (4119) [INFO] * 2023-08-27 22:15:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-27 22:15:32 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-27 22:15:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-27 22:15:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r0tDkDJTAQ/ea_profile.json * 2023-08-27 22:15:59 (2259) [INFO] Backed up EA4 profile to /tmp/r0tDkDJTAQ/ea_profile.json * 2023-08-27 22:16: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-27 22:16:00 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-28 22:14:17 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-28 22:14:18 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-28 22:14:18 (1700) [INFO] Checking if your system is up to date: * 2023-08-28 22:14:18 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-28 22:14:18 (4089) [INFO] * 2023-08-28 22:14:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-28 22:14:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-28 22:14:18 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-28 22:14:18 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-28 22:14:18 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-28 22:14:18 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-28 22:14:18 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-28 22:14:18 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-28 22:14:18 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-28 22:14:18 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-28 22:14:18 (4119) [INFO] * 2023-08-28 22:14:18 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-28 22:14:18 (4089) [INFO] * 2023-08-28 22:14:41 (4102) [INFO] * 2023-08-28 22:14:41 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-28 22:14:41 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-28 22:14:41 (4119) [INFO] * 2023-08-28 22:14:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-28 22:14:41 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-28 22:15:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-28 22:15:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cxHKNwtCWo/ea_profile.json * 2023-08-28 22:15:10 (2259) [INFO] Backed up EA4 profile to /tmp/cxHKNwtCWo/ea_profile.json * 2023-08-28 22:15: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-08-28 22:15:10 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-29 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-29 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-29 22:14:04 (1700) [INFO] Checking if your system is up to date: * 2023-08-29 22:14:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-29 22:14:04 (4089) [INFO] * 2023-08-29 22:14:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-29 22:14:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-29 22:14:04 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-29 22:14:04 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-29 22:14:04 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-29 22:14:04 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-29 22:14:04 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-29 22:14:04 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-29 22:14:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-29 22:14:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-29 22:14:05 (4119) [INFO] * 2023-08-29 22:14:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-29 22:14:05 (4089) [INFO] * 2023-08-29 22:14:28 (4102) [INFO] * 2023-08-29 22:14:28 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-29 22:14:28 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-29 22:14:28 (4119) [INFO] * 2023-08-29 22:14:28 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-29 22:14:28 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-29 22:14:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-29 22:14:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TYFIrwbY9R/ea_profile.json * 2023-08-29 22:14:58 (2259) [INFO] Backed up EA4 profile to /tmp/TYFIrwbY9R/ea_profile.json * 2023-08-29 22:14: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-29 22:14:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-30 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-30 22:14:20 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-30 22:14:20 (1700) [INFO] Checking if your system is up to date: * 2023-08-30 22:14:20 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-30 22:14:20 (4089) [INFO] * 2023-08-30 22:14:21 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-30 22:14:21 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-30 22:14:21 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-30 22:14:21 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-30 22:14:21 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-30 22:14:21 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-30 22:14:21 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-30 22:14:21 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-30 22:14:21 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-30 22:14:21 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-30 22:14:21 (4119) [INFO] * 2023-08-30 22:14:21 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-30 22:14:21 (4089) [INFO] * 2023-08-30 22:14:43 (4102) [INFO] * 2023-08-30 22:14:43 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-30 22:14:43 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-30 22:14:43 (4119) [INFO] * 2023-08-30 22:14:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-30 22:14:43 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-30 22:15:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-30 22:15:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KF2mrPrv5G/ea_profile.json * 2023-08-30 22:15:10 (2259) [INFO] Backed up EA4 profile to /tmp/KF2mrPrv5G/ea_profile.json * 2023-08-30 22:15: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-30 22:15:11 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-08-31 22:14:35 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-08-31 22:14:35 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-08-31 22:14:35 (1700) [INFO] Checking if your system is up to date: * 2023-08-31 22:14:35 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-08-31 22:14:35 (4089) [INFO] * 2023-08-31 22:14:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-08-31 22:14:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-08-31 22:14:36 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-08-31 22:14:36 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-08-31 22:14:36 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-08-31 22:14:36 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-08-31 22:14:36 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-08-31 22:14:36 (4102) [INFO] : wp-toolkit-thirdparties * 2023-08-31 22:14:36 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-08-31 22:14:36 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-08-31 22:14:36 (4119) [INFO] * 2023-08-31 22:14:36 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-08-31 22:14:36 (4089) [INFO] * 2023-08-31 22:15:13 (4102) [INFO] * 2023-08-31 22:15:13 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-08-31 22:15:13 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-08-31 22:15:13 (4119) [INFO] * 2023-08-31 22:15:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-08-31 22:15:13 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-08-31 22:15:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-08-31 22:15:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cW2EP1lMuv/ea_profile.json * 2023-08-31 22:15:37 (2259) [INFO] Backed up EA4 profile to /tmp/cW2EP1lMuv/ea_profile.json * 2023-08-31 22:15: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-08-31 22:15:38 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-01 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-09-01 22:14:06 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-01 22:14:06 (1700) [INFO] Checking if your system is up to date: * 2023-09-01 22:14:06 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-01 22:14:06 (4089) [INFO] * 2023-09-01 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-01 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-01 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-01 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-01 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-01 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-01 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-01 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-01 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-01 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-01 22:14:06 (4119) [INFO] * 2023-09-01 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-01 22:14:06 (4089) [INFO] * 2023-09-01 22:14:30 (4102) [INFO] * 2023-09-01 22:14:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-01 22:14:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-01 22:14:30 (4119) [INFO] * 2023-09-01 22:14:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-01 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-01 22:14:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-01 22:14:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vby61rmKsk/ea_profile.json * 2023-09-01 22:14:55 (2259) [INFO] Backed up EA4 profile to /tmp/vby61rmKsk/ea_profile.json * 2023-09-01 22:14: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-01 22:14:55 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-02 22:15:08 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-09-02 22:15:09 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-02 22:15:09 (1700) [INFO] Checking if your system is up to date: * 2023-09-02 22:15:09 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-02 22:15:09 (4089) [INFO] * 2023-09-02 22:15:09 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-02 22:15:09 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-02 22:15:09 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-02 22:15:09 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-02 22:15:09 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-02 22:15:09 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-02 22:15:09 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-02 22:15:09 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-02 22:15:09 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-02 22:15:09 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-02 22:15:09 (4119) [INFO] * 2023-09-02 22:15:09 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-02 22:15:09 (4089) [INFO] * 2023-09-02 22:15:33 (4102) [INFO] * 2023-09-02 22:15:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-02 22:15:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-02 22:15:33 (4119) [INFO] * 2023-09-02 22:15:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-02 22:15:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-02 22:16:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-02 22:16:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I3Lhe0UfEI/ea_profile.json * 2023-09-02 22:16:01 (2259) [INFO] Backed up EA4 profile to /tmp/I3Lhe0UfEI/ea_profile.json * 2023-09-02 22:16: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-09-02 22:16:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-03 22:14:59 (153) [WARN] *** Elevation Blocker detected: *** disk space issue * 2023-09-03 22:14:59 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-03 22:14:59 (1700) [INFO] Checking if your system is up to date: * 2023-09-03 22:14:59 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-03 22:14:59 (4089) [INFO] * 2023-09-03 22:14:59 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-03 22:14:59 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-03 22:14:59 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-03 22:14:59 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-03 22:14:59 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-03 22:14:59 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-03 22:14:59 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-03 22:14:59 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-03 22:14:59 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-03 22:14:59 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-03 22:14:59 (4119) [INFO] * 2023-09-03 22:14:59 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-03 22:14:59 (4089) [INFO] * 2023-09-03 22:15:24 (4102) [INFO] * 2023-09-03 22:15:24 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-03 22:15:24 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-03 22:15:24 (4119) [INFO] * 2023-09-03 22:15:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-03 22:15:24 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-03 22:15:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-03 22:15:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/E6esuvh8pq/ea_profile.json * 2023-09-03 22:15:49 (2259) [INFO] Backed up EA4 profile to /tmp/E6esuvh8pq/ea_profile.json * 2023-09-03 22:15: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-09-03 22:15:50 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-04 22:14:04 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-04 22:14:04 (1700) [INFO] Checking if your system is up to date: * 2023-09-04 22:14:04 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-04 22:14:04 (4089) [INFO] * 2023-09-04 22:14:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-04 22:14:05 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-04 22:14:05 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-04 22:14:05 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-04 22:14:05 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-04 22:14:05 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-04 22:14:05 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-04 22:14:05 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-04 22:14:05 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-04 22:14:05 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-04 22:14:05 (4119) [INFO] * 2023-09-04 22:14:05 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-04 22:14:05 (4089) [INFO] * 2023-09-04 22:14:26 (4102) [INFO] * 2023-09-04 22:14:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-04 22:14:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-04 22:14:26 (4119) [INFO] * 2023-09-04 22:14:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-04 22:14:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-04 22:14:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-04 22:14:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TE2fvd0cbg/ea_profile.json * 2023-09-04 22:14:53 (2259) [INFO] Backed up EA4 profile to /tmp/TE2fvd0cbg/ea_profile.json * 2023-09-04 22:14: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-09-04 22:14:53 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-05 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-05 22:14:05 (1700) [INFO] Checking if your system is up to date: * 2023-09-05 22:14:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-05 22:14:05 (4089) [INFO] * 2023-09-05 22:14:06 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-05 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-05 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-05 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-05 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-05 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-05 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-05 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-05 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-05 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-05 22:14:06 (4119) [INFO] * 2023-09-05 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-05 22:14:06 (4089) [INFO] * 2023-09-05 22:14:30 (4102) [INFO] * 2023-09-05 22:14:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-05 22:14:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-05 22:14:30 (4119) [INFO] * 2023-09-05 22:14:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-05 22:14:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-05 22:14:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-05 22:14:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y5uxNVWc2c/ea_profile.json * 2023-09-05 22:14:53 (2259) [INFO] Backed up EA4 profile to /tmp/y5uxNVWc2c/ea_profile.json * 2023-09-05 22:14: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-09-05 22:14:54 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-06 22:14:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-06 22:14:07 (1700) [INFO] Checking if your system is up to date: * 2023-09-06 22:14:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-06 22:14:07 (4089) [INFO] * 2023-09-06 22:14:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-06 22:14:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-06 22:14:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-06 22:14:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-06 22:14:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-06 22:14:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-06 22:14:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-06 22:14:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-06 22:14:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-06 22:14:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-06 22:14:07 (4119) [INFO] * 2023-09-06 22:14:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-06 22:14:07 (4089) [INFO] * 2023-09-06 22:14:29 (4102) [INFO] * 2023-09-06 22:14:29 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-06 22:14:29 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-06 22:14:29 (4119) [INFO] * 2023-09-06 22:14:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-06 22:14:29 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-06 22:14:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-06 22:14:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gFb9E9zsd3/ea_profile.json * 2023-09-06 22:14:55 (2259) [INFO] Backed up EA4 profile to /tmp/gFb9E9zsd3/ea_profile.json * 2023-09-06 22:14: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-06 22:14:55 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-07 22:14:05 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-07 22:14:05 (1700) [INFO] Checking if your system is up to date: * 2023-09-07 22:14:05 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-07 22:14:05 (4089) [INFO] * 2023-09-07 22:14:05 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-07 22:14:06 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-07 22:14:06 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-07 22:14:06 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-07 22:14:06 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-07 22:14:06 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-07 22:14:06 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-07 22:14:06 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-07 22:14:06 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-07 22:14:06 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-07 22:14:06 (4119) [INFO] * 2023-09-07 22:14:06 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-07 22:14:06 (4089) [INFO] * 2023-09-07 22:14:26 (4102) [INFO] * 2023-09-07 22:14:26 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-07 22:14:26 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-07 22:14:26 (4119) [INFO] * 2023-09-07 22:14:26 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-07 22:14:26 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-07 22:14:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-07 22:14:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xZDGynMQF4/ea_profile.json * 2023-09-07 22:14:53 (2259) [INFO] Backed up EA4 profile to /tmp/xZDGynMQF4/ea_profile.json * 2023-09-07 22:14: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-09-07 22:14:54 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-08 22:14:08 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-08 22:14:08 (1700) [INFO] Checking if your system is up to date: * 2023-09-08 22:14:08 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-08 22:14:08 (4089) [INFO] * 2023-09-08 22:14:08 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-08 22:14:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-08 22:14:08 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-08 22:14:08 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-08 22:14:08 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-08 22:14:08 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-08 22:14:08 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-08 22:14:08 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-08 22:14:08 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-08 22:14:08 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-08 22:14:08 (4119) [INFO] * 2023-09-08 22:14:08 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-08 22:14:08 (4089) [INFO] * 2023-09-08 22:14:33 (4102) [INFO] * 2023-09-08 22:14:33 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-08 22:14:33 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-08 22:14:33 (4119) [INFO] * 2023-09-08 22:14:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-08 22:14:33 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-08 22:14:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-08 22:14:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ENHcUJr52K/ea_profile.json * 2023-09-08 22:15:00 (2259) [INFO] Backed up EA4 profile to /tmp/ENHcUJr52K/ea_profile.json * 2023-09-08 22:15: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-09-08 22:15:01 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-09 22:15:07 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-09 22:15:07 (1700) [INFO] Checking if your system is up to date: * 2023-09-09 22:15:07 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-09 22:15:07 (4089) [INFO] * 2023-09-09 22:15:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-09 22:15:07 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-09 22:15:07 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-09 22:15:07 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-09 22:15:07 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-09 22:15:07 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-09 22:15:07 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-09 22:15:07 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-09 22:15:07 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-09 22:15:07 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-09 22:15:07 (4119) [INFO] * 2023-09-09 22:15:07 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-09 22:15:07 (4089) [INFO] * 2023-09-09 22:15:30 (4102) [INFO] * 2023-09-09 22:15:30 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-09 22:15:30 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-09 22:15:30 (4119) [INFO] * 2023-09-09 22:15:30 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-09 22:15:30 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-09 22:15:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-09 22:15:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JTRTcyFPIl/ea_profile.json * 2023-09-09 22:15:58 (2259) [INFO] Backed up EA4 profile to /tmp/JTRTcyFPIl/ea_profile.json * 2023-09-09 22:15: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-09-09 22:15:59 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-10 22:14:57 (153) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-10 22:14:57 (1700) [INFO] Checking if your system is up to date: * 2023-09-10 22:14:57 (4088) [INFO] Running: /usr/bin/yum clean all * 2023-09-10 22:14:57 (4089) [INFO] * 2023-09-10 22:14:58 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-10 22:14:58 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-10 22:14:58 (4102) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-10 22:14:58 (4102) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-10 22:14:58 (4102) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-10 22:14:58 (4102) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-10 22:14:58 (4102) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-10 22:14:58 (4102) [INFO] : wp-toolkit-thirdparties * 2023-09-10 22:14:58 (4102) [INFO] Cleaning up list of fastest mirrors * 2023-09-10 22:14:58 (4102) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-10 22:14:58 (4119) [INFO] * 2023-09-10 22:14:58 (4088) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-10 22:14:58 (4089) [INFO] * 2023-09-10 22:15:21 (4102) [INFO] * 2023-09-10 22:15:21 (4102) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-10 22:15:21 (4102) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-10 22:15:21 (4119) [INFO] * 2023-09-10 22:15:21 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-10 22:15:21 (153) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-10 22:15:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-10 22:15:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ieSlLBxrAU/ea_profile.json * 2023-09-10 22:15:48 (2259) [INFO] Backed up EA4 profile to /tmp/ieSlLBxrAU/ea_profile.json * 2023-09-10 22:15: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-09-10 22:15:49 (258) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-11 22:14:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-11 22:14:05 (1752) [INFO] Checking if your system is up to date: * 2023-09-11 22:14:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-11 22:14:05 (4229) [INFO] * 2023-09-11 22:14:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-11 22:14:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-11 22:14:05 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-11 22:14:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-11 22:14:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-11 22:14:05 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-11 22:14:05 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-11 22:14:05 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-11 22:14:05 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-11 22:14:05 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-11 22:14:05 (4259) [INFO] * 2023-09-11 22:14:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-11 22:14:05 (4229) [INFO] * 2023-09-11 22:14:29 (4242) [INFO] * 2023-09-11 22:14:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-11 22:14:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-11 22:14:29 (4259) [INFO] * 2023-09-11 22:14:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-11 22:14:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-11 22:14:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-11 22:14:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yXpCAIfQPG/ea_profile.json * 2023-09-11 22:14:55 (2293) [INFO] Backed up EA4 profile to /tmp/yXpCAIfQPG/ea_profile.json * 2023-09-11 22:14: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-11 22:14:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-12 22:14:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-12 22:14:05 (1752) [INFO] Checking if your system is up to date: * 2023-09-12 22:14:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-12 22:14:05 (4229) [INFO] * 2023-09-12 22:14:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-12 22:14:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-12 22:14:05 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-12 22:14:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-12 22:14:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-12 22:14:05 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-12 22:14:05 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-12 22:14:05 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-12 22:14:05 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-12 22:14:05 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-12 22:14:05 (4259) [INFO] * 2023-09-12 22:14:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-12 22:14:05 (4229) [INFO] * 2023-09-12 22:14:27 (4242) [INFO] * 2023-09-12 22:14:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-12 22:14:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-12 22:14:27 (4259) [INFO] * 2023-09-12 22:14:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-12 22:14:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-12 22:14:54 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-12 22:14:54 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J9HLh1tDbz/ea_profile.json * 2023-09-12 22:14:55 (2293) [INFO] Backed up EA4 profile to /tmp/J9HLh1tDbz/ea_profile.json * 2023-09-12 22:14:56 (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 22:14:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-13 22:15:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-13 22:15:49 (1752) [INFO] Checking if your system is up to date: * 2023-09-13 22:15:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-13 22:15:49 (4229) [INFO] * 2023-09-13 22:15:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-13 22:15:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-13 22:15:49 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-13 22:15:49 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-13 22:15:49 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-13 22:15:49 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-13 22:15:49 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-13 22:15:49 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-13 22:15:49 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-13 22:15:49 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-13 22:15:49 (4259) [INFO] * 2023-09-13 22:15:49 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-13 22:15:49 (4229) [INFO] * 2023-09-13 22:16:13 (4242) [INFO] * 2023-09-13 22:16:13 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-13 22:16:13 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-13 22:16:13 (4259) [INFO] * 2023-09-13 22:16:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-13 22:16:13 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-13 22:16:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-13 22:16:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xaMrknypcB/ea_profile.json * 2023-09-13 22:16:38 (2293) [INFO] Backed up EA4 profile to /tmp/xaMrknypcB/ea_profile.json * 2023-09-13 22:16: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-13 22:16:39 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-14 22:14:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-14 22:14:19 (1752) [INFO] Checking if your system is up to date: * 2023-09-14 22:14:19 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-14 22:14:19 (4229) [INFO] * 2023-09-14 22:14:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-14 22:14:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-14 22:14:19 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-14 22:14:19 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-14 22:14:19 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-14 22:14:19 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-14 22:14:19 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-14 22:14:19 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-14 22:14:19 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-14 22:14:19 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-14 22:14:19 (4259) [INFO] * 2023-09-14 22:14:19 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-14 22:14:19 (4229) [INFO] * 2023-09-14 22:14:43 (4242) [INFO] * 2023-09-14 22:14:43 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-14 22:14:43 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-14 22:14:43 (4259) [INFO] * 2023-09-14 22:14:43 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-14 22:14:43 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-14 22:15:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-14 22:15:08 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ggk3BCcUjX/ea_profile.json * 2023-09-14 22:15:09 (2293) [INFO] Backed up EA4 profile to /tmp/ggk3BCcUjX/ea_profile.json * 2023-09-14 22:15:13 (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 22:15:13 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-15 22:14:06 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-15 22:14:06 (1752) [INFO] Checking if your system is up to date: * 2023-09-15 22:14:06 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-15 22:14:06 (4229) [INFO] * 2023-09-15 22:14:07 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-15 22:14:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-15 22:14:07 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-15 22:14:07 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-15 22:14:07 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-15 22:14:07 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-15 22:14:07 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-15 22:14:07 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-15 22:14:07 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-15 22:14:07 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-15 22:14:07 (4259) [INFO] * 2023-09-15 22:14:07 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-15 22:14:07 (4229) [INFO] * 2023-09-15 22:14:30 (4242) [INFO] * 2023-09-15 22:14:30 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-15 22:14:30 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-15 22:14:30 (4259) [INFO] * 2023-09-15 22:14:30 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-15 22:14:30 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-15 22:14:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-15 22:14:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Xo_gFOXtmH/ea_profile.json * 2023-09-15 22:14:57 (2293) [INFO] Backed up EA4 profile to /tmp/Xo_gFOXtmH/ea_profile.json * 2023-09-15 22:14: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-09-15 22:14:58 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-16 22:15:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-16 22:15:05 (1752) [INFO] Checking if your system is up to date: * 2023-09-16 22:15:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-16 22:15:05 (4229) [INFO] * 2023-09-16 22:15:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-16 22:15:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-16 22:15:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-16 22:15:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-16 22:15:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-16 22:15:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-16 22:15:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-16 22:15:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-16 22:15:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-16 22:15:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-16 22:15:06 (4259) [INFO] * 2023-09-16 22:15:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-16 22:15:06 (4229) [INFO] * 2023-09-16 22:15:29 (4242) [INFO] * 2023-09-16 22:15:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-16 22:15:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-16 22:15:29 (4259) [INFO] * 2023-09-16 22:15:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-16 22:15:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-16 22:15:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-16 22:15:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0wRd1m4hMJ/ea_profile.json * 2023-09-16 22:15:53 (2293) [INFO] Backed up EA4 profile to /tmp/0wRd1m4hMJ/ea_profile.json * 2023-09-16 22:15: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-16 22:15:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-17 22:15:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-17 22:15:04 (1752) [INFO] Checking if your system is up to date: * 2023-09-17 22:15:04 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-17 22:15:04 (4229) [INFO] * 2023-09-17 22:15:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-17 22:15:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-17 22:15:04 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-17 22:15:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-17 22:15:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-17 22:15:04 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-17 22:15:04 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-17 22:15:04 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-17 22:15:04 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-17 22:15:04 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-17 22:15:04 (4259) [INFO] * 2023-09-17 22:15:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-17 22:15:04 (4229) [INFO] * 2023-09-17 22:15:27 (4242) [INFO] * 2023-09-17 22:15:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-17 22:15:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-17 22:15:27 (4259) [INFO] * 2023-09-17 22:15:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-17 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-17 22:15:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-17 22:15:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JhwLN2554K/ea_profile.json * 2023-09-17 22:15:52 (2293) [INFO] Backed up EA4 profile to /tmp/JhwLN2554K/ea_profile.json * 2023-09-17 22:15: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-09-17 22:15:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-18 22:14:08 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-18 22:14:08 (1752) [INFO] Checking if your system is up to date: * 2023-09-18 22:14:08 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-18 22:14:08 (4229) [INFO] * 2023-09-18 22:14:08 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-18 22:14:08 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-18 22:14:08 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-18 22:14:08 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-18 22:14:08 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-18 22:14:08 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-18 22:14:08 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-18 22:14:08 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-18 22:14:08 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-18 22:14:08 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-18 22:14:08 (4259) [INFO] * 2023-09-18 22:14:08 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-18 22:14:08 (4229) [INFO] * 2023-09-18 22:14:30 (4242) [INFO] * 2023-09-18 22:14:30 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-18 22:14:30 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-18 22:14:30 (4259) [INFO] * 2023-09-18 22:14:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-18 22:14:31 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-18 22:14:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-18 22:14:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TWSZHJOMi9/ea_profile.json * 2023-09-18 22:14:58 (2293) [INFO] Backed up EA4 profile to /tmp/TWSZHJOMi9/ea_profile.json * 2023-09-18 22:14:59 (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 22:14:59 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-19 22:14:06 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-19 22:14:06 (1752) [INFO] Checking if your system is up to date: * 2023-09-19 22:14:06 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-19 22:14:06 (4229) [INFO] * 2023-09-19 22:14:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-19 22:14:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-19 22:14:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-19 22:14:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-19 22:14:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-19 22:14:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-19 22:14:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-19 22:14:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-19 22:14:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-19 22:14:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-19 22:14:06 (4259) [INFO] * 2023-09-19 22:14:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-19 22:14:06 (4229) [INFO] * 2023-09-19 22:14:27 (4242) [INFO] * 2023-09-19 22:14:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-19 22:14:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-19 22:14:27 (4259) [INFO] * 2023-09-19 22:14:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-19 22:14:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-19 22:14:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-19 22:14:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XdWYqrleRC/ea_profile.json * 2023-09-19 22:14:53 (2293) [INFO] Backed up EA4 profile to /tmp/XdWYqrleRC/ea_profile.json * 2023-09-19 22:14: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-19 22:14:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-20 22:14:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-20 22:14:04 (1752) [INFO] Checking if your system is up to date: * 2023-09-20 22:14:04 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-20 22:14:04 (4229) [INFO] * 2023-09-20 22:14:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-20 22:14:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-20 22:14:04 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-20 22:14:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-20 22:14:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-20 22:14:04 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-20 22:14:04 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-20 22:14:04 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-20 22:14:04 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-20 22:14:04 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-20 22:14:04 (4259) [INFO] * 2023-09-20 22:14:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-20 22:14:04 (4229) [INFO] * 2023-09-20 22:14:26 (4242) [INFO] * 2023-09-20 22:14:26 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-20 22:14:26 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-20 22:14:26 (4259) [INFO] * 2023-09-20 22:14:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-20 22:14:26 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-20 22:14:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-20 22:14:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yVJEEkMCJV/ea_profile.json * 2023-09-20 22:14:51 (2293) [INFO] Backed up EA4 profile to /tmp/yVJEEkMCJV/ea_profile.json * 2023-09-20 22:14: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-09-20 22:14:52 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-21 22:15:47 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-21 22:15:47 (1752) [INFO] Checking if your system is up to date: * 2023-09-21 22:15:47 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-21 22:15:47 (4229) [INFO] * 2023-09-21 22:15:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-21 22:15:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-21 22:15:47 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-21 22:15:47 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-21 22:15:47 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-21 22:15:47 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-21 22:15:47 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-21 22:15:47 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-21 22:15:47 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-21 22:15:47 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-21 22:15:47 (4259) [INFO] * 2023-09-21 22:15:47 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-21 22:15:47 (4229) [INFO] * 2023-09-21 22:16:12 (4242) [INFO] * 2023-09-21 22:16:12 (4242) [INFO] kernel.x86_64 3.10.0-1160.95.1.el7 updates * 2023-09-21 22:16:12 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-21 22:16:12 (4259) [INFO] * 2023-09-21 22:16:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-21 22:16:12 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-21 22:16:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-21 22:16:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4DYZRvCg18/ea_profile.json * 2023-09-21 22:16:39 (2293) [INFO] Backed up EA4 profile to /tmp/4DYZRvCg18/ea_profile.json * 2023-09-21 22:16: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-21 22:16:40 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-22 22:14:23 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-22 22:14:23 (1752) [INFO] Checking if your system is up to date: * 2023-09-22 22:14:23 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-22 22:14:23 (4229) [INFO] * 2023-09-22 22:14:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-22 22:14:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-22 22:14:23 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-22 22:14:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-22 22:14:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-22 22:14:23 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-22 22:14:23 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-22 22:14:23 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-22 22:14:23 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-22 22:14:23 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-22 22:14:23 (4259) [INFO] * 2023-09-22 22:14:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-22 22:14:23 (4229) [INFO] * 2023-09-22 22:14:46 (4242) [INFO] * 2023-09-22 22:14:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-22 22:14:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-22 22:14:46 (4259) [INFO] * 2023-09-22 22:14:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-22 22:14:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-22 22:15:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-22 22:15:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JiW8k_mJFC/ea_profile.json * 2023-09-22 22:15:15 (2293) [INFO] Backed up EA4 profile to /tmp/JiW8k_mJFC/ea_profile.json * 2023-09-22 22:15:15 (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 22:15:15 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-23 22:15:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-23 22:15:05 (1752) [INFO] Checking if your system is up to date: * 2023-09-23 22:15:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-23 22:15:05 (4229) [INFO] * 2023-09-23 22:15:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-23 22:15:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-23 22:15:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-23 22:15:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-23 22:15:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-23 22:15:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-23 22:15:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-23 22:15:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-23 22:15:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-23 22:15:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-23 22:15:06 (4259) [INFO] * 2023-09-23 22:15:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-23 22:15:06 (4229) [INFO] * 2023-09-23 22:15:29 (4242) [INFO] * 2023-09-23 22:15:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-23 22:15:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-23 22:15:29 (4259) [INFO] * 2023-09-23 22:15:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-23 22:15:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-23 22:15:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-23 22:15:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BRZXO35EH2/ea_profile.json * 2023-09-23 22:16:00 (2293) [INFO] Backed up EA4 profile to /tmp/BRZXO35EH2/ea_profile.json * 2023-09-23 22:16: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-09-23 22:16:01 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-24 22:15:06 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-24 22:15:06 (1752) [INFO] Checking if your system is up to date: * 2023-09-24 22:15:06 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-24 22:15:06 (4229) [INFO] * 2023-09-24 22:15:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-24 22:15:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-24 22:15:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-24 22:15:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-24 22:15:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-24 22:15:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-24 22:15:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-24 22:15:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-24 22:15:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-24 22:15:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-24 22:15:06 (4259) [INFO] * 2023-09-24 22:15:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-24 22:15:06 (4229) [INFO] * 2023-09-24 22:15:31 (4242) [INFO] * 2023-09-24 22:15:31 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-24 22:15:31 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-24 22:15:31 (4259) [INFO] * 2023-09-24 22:15:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-24 22:15:31 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-24 22:15:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-24 22:15:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dcJf_h73Lt/ea_profile.json * 2023-09-24 22:15:57 (2293) [INFO] Backed up EA4 profile to /tmp/dcJf_h73Lt/ea_profile.json * 2023-09-24 22:15: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-09-24 22:15:58 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-25 22:14:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-25 22:14:05 (1752) [INFO] Checking if your system is up to date: * 2023-09-25 22:14:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-25 22:14:05 (4229) [INFO] * 2023-09-25 22:14:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-25 22:14:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-25 22:14:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-25 22:14:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-25 22:14:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-25 22:14:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-25 22:14:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-25 22:14:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-25 22:14:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-25 22:14:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-25 22:14:06 (4259) [INFO] * 2023-09-25 22:14:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-25 22:14:06 (4229) [INFO] * 2023-09-25 22:14:28 (4242) [INFO] * 2023-09-25 22:14:28 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-25 22:14:28 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-25 22:14:28 (4259) [INFO] * 2023-09-25 22:14:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-25 22:14:28 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-25 22:14:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-25 22:14:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/awkoShU9hy/ea_profile.json * 2023-09-25 22:14:56 (2293) [INFO] Backed up EA4 profile to /tmp/awkoShU9hy/ea_profile.json * 2023-09-25 22:14: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-09-25 22:14:57 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-26 22:14:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-26 22:14:14 (1752) [INFO] Checking if your system is up to date: * 2023-09-26 22:14:14 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-26 22:14:14 (4229) [INFO] * 2023-09-26 22:14:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-26 22:14:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-26 22:14:14 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-26 22:14:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-26 22:14:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-26 22:14:14 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-26 22:14:14 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-26 22:14:14 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-26 22:14:14 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-26 22:14:14 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-26 22:14:14 (4259) [INFO] * 2023-09-26 22:14:14 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-26 22:14:14 (4229) [INFO] * 2023-09-26 22:14:35 (4242) [INFO] * 2023-09-26 22:14:35 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-26 22:14:35 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-26 22:14:35 (4259) [INFO] * 2023-09-26 22:14:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-26 22:14:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-26 22:14:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-26 22:14:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GkKde5_Tw1/ea_profile.json * 2023-09-26 22:15:00 (2293) [INFO] Backed up EA4 profile to /tmp/GkKde5_Tw1/ea_profile.json * 2023-09-26 22:15: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-09-26 22:15:02 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-27 22:14:26 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-27 22:14:26 (1752) [INFO] Checking if your system is up to date: * 2023-09-27 22:14:26 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-27 22:14:26 (4229) [INFO] * 2023-09-27 22:14:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-27 22:14:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-27 22:14:27 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-27 22:14:27 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-27 22:14:27 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-27 22:14:27 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-27 22:14:27 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-27 22:14:27 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-27 22:14:27 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-27 22:14:27 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-27 22:14:27 (4259) [INFO] * 2023-09-27 22:14:27 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-27 22:14:27 (4229) [INFO] * 2023-09-27 22:14:51 (4242) [INFO] * 2023-09-27 22:14:51 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-27 22:14:51 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-27 22:14:51 (4259) [INFO] * 2023-09-27 22:14:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-27 22:14:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-27 22:15:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-27 22:15:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6dDSmK_iU6/ea_profile.json * 2023-09-27 22:15:17 (2293) [INFO] Backed up EA4 profile to /tmp/6dDSmK_iU6/ea_profile.json * 2023-09-27 22:15:18 (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 22:15:18 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-28 22:14:02 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-28 22:14:02 (1752) [INFO] Checking if your system is up to date: * 2023-09-28 22:14:02 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-28 22:14:02 (4229) [INFO] * 2023-09-28 22:14:02 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-28 22:14:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-28 22:14:02 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-28 22:14:02 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-28 22:14:02 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-28 22:14:02 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-28 22:14:02 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-28 22:14:02 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-28 22:14:02 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-28 22:14:02 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-28 22:14:02 (4259) [INFO] * 2023-09-28 22:14:02 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-28 22:14:02 (4229) [INFO] * 2023-09-28 22:14:25 (4242) [INFO] * 2023-09-28 22:14:25 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-28 22:14:25 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-28 22:14:25 (4259) [INFO] * 2023-09-28 22:14:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-28 22:14:25 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-28 22:14:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-28 22:14:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DzjXDyXlsY/ea_profile.json * 2023-09-28 22:14:49 (2293) [INFO] Backed up EA4 profile to /tmp/DzjXDyXlsY/ea_profile.json * 2023-09-28 22:14: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-28 22:14:50 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-29 22:14:07 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-29 22:14:07 (1752) [INFO] Checking if your system is up to date: * 2023-09-29 22:14:07 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-29 22:14:07 (4229) [INFO] * 2023-09-29 22:14:07 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-29 22:14:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-29 22:14:07 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-29 22:14:07 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-29 22:14:07 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-29 22:14:07 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-29 22:14:07 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-29 22:14:07 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-29 22:14:07 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-29 22:14:07 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-29 22:14:07 (4259) [INFO] * 2023-09-29 22:14:07 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-29 22:14:07 (4229) [INFO] * 2023-09-29 22:14:31 (4242) [INFO] * 2023-09-29 22:14:31 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-29 22:14:31 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-29 22:14:31 (4259) [INFO] * 2023-09-29 22:14:31 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-29 22:14:31 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-29 22:14:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-29 22:15:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R6oeXT1Jop/ea_profile.json * 2023-09-29 22:15:01 (2293) [INFO] Backed up EA4 profile to /tmp/R6oeXT1Jop/ea_profile.json * 2023-09-29 22:15: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-29 22:15:02 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-09-30 22:15:18 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-09-30 22:15:18 (1752) [INFO] Checking if your system is up to date: * 2023-09-30 22:15:18 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-09-30 22:15:18 (4229) [INFO] * 2023-09-30 22:15:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-09-30 22:15:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-09-30 22:15:19 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-09-30 22:15:19 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-09-30 22:15:19 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-09-30 22:15:19 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-09-30 22:15:19 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-09-30 22:15:19 (4242) [INFO] : wp-toolkit-thirdparties * 2023-09-30 22:15:19 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-09-30 22:15:19 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-09-30 22:15:19 (4259) [INFO] * 2023-09-30 22:15:19 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-09-30 22:15:19 (4229) [INFO] * 2023-09-30 22:15:48 (4242) [INFO] * 2023-09-30 22:15:48 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-09-30 22:15:48 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-09-30 22:15:48 (4259) [INFO] * 2023-09-30 22:15:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-09-30 22:15:48 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-09-30 22:16:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-09-30 22:16:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mlZyfsjSPB/ea_profile.json * 2023-09-30 22:16:21 (2293) [INFO] Backed up EA4 profile to /tmp/mlZyfsjSPB/ea_profile.json * 2023-09-30 22:16: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-30 22:16:22 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-01 22:15:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-01 22:15:05 (1752) [INFO] Checking if your system is up to date: * 2023-10-01 22:15:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-01 22:15:05 (4229) [INFO] * 2023-10-01 22:15:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-01 22:15:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-01 22:15:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-01 22:15:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-01 22:15:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-01 22:15:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-01 22:15:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-01 22:15:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-01 22:15:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-01 22:15:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-01 22:15:06 (4259) [INFO] * 2023-10-01 22:15:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-01 22:15:06 (4229) [INFO] * 2023-10-01 22:15:30 (4242) [INFO] * 2023-10-01 22:15:30 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-01 22:15:30 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-01 22:15:30 (4259) [INFO] * 2023-10-01 22:15:30 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-01 22:15:30 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-01 22:15:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-01 22:15:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EPtIYdPuVN/ea_profile.json * 2023-10-01 22:15:59 (2293) [INFO] Backed up EA4 profile to /tmp/EPtIYdPuVN/ea_profile.json * 2023-10-01 22:15:59 (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 22:15:59 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-02 22:15:47 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-02 22:15:47 (1752) [INFO] Checking if your system is up to date: * 2023-10-02 22:15:47 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-02 22:15:47 (4229) [INFO] * 2023-10-02 22:15:47 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-02 22:15:47 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-02 22:15:47 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-02 22:15:47 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-02 22:15:47 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-02 22:15:47 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-02 22:15:47 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-02 22:15:47 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-02 22:15:47 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-02 22:15:47 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-02 22:15:47 (4259) [INFO] * 2023-10-02 22:15:47 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-02 22:15:47 (4229) [INFO] * 2023-10-02 22:16:12 (4242) [INFO] * 2023-10-02 22:16:12 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-02 22:16:12 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-02 22:16:13 (4259) [INFO] * 2023-10-02 22:16:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-02 22:16:13 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-02 22:16:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-02 22:16:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ybzYmlDfLZ/ea_profile.json * 2023-10-02 22:16:38 (2293) [INFO] Backed up EA4 profile to /tmp/ybzYmlDfLZ/ea_profile.json * 2023-10-02 22:16: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-10-02 22:16:38 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-03 22:14:11 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-03 22:14:11 (1752) [INFO] Checking if your system is up to date: * 2023-10-03 22:14:11 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-03 22:14:11 (4229) [INFO] * 2023-10-03 22:14:11 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-03 22:14:11 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-03 22:14:11 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-03 22:14:11 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-03 22:14:11 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-03 22:14:11 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-03 22:14:11 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-03 22:14:11 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-03 22:14:11 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-03 22:14:11 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-03 22:14:11 (4259) [INFO] * 2023-10-03 22:14:11 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-03 22:14:11 (4229) [INFO] * 2023-10-03 22:14:35 (4242) [INFO] * 2023-10-03 22:14:35 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-03 22:14:35 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-03 22:14:35 (4259) [INFO] * 2023-10-03 22:14:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-03 22:14:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-03 22:15:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-03 22:15:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k43HPOu6I6/ea_profile.json * 2023-10-03 22:15:13 (2293) [INFO] Backed up EA4 profile to /tmp/k43HPOu6I6/ea_profile.json * 2023-10-03 22:15: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-03 22:15:14 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-04 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-04 22:15:27 (1752) [INFO] Checking if your system is up to date: * 2023-10-04 22:15:27 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-04 22:15:27 (4229) [INFO] * 2023-10-04 22:15:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-04 22:15:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-04 22:15:28 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-04 22:15:28 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-04 22:15:28 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-04 22:15:28 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-04 22:15:28 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-04 22:15:28 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-04 22:15:28 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-04 22:15:28 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-04 22:15:28 (4259) [INFO] * 2023-10-04 22:15:28 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-04 22:15:28 (4229) [INFO] * 2023-10-04 22:15:54 (4242) [INFO] * 2023-10-04 22:15:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-04 22:15:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-04 22:15:54 (4259) [INFO] * 2023-10-04 22:15:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-04 22:15:54 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-04 22:16:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-04 22:16:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nOm_NlN5K9/ea_profile.json * 2023-10-04 22:16:26 (2293) [INFO] Backed up EA4 profile to /tmp/nOm_NlN5K9/ea_profile.json * 2023-10-04 22:16: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-04 22:16:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-05 22:14:10 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-05 22:14:10 (1752) [INFO] Checking if your system is up to date: * 2023-10-05 22:14:10 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-05 22:14:10 (4229) [INFO] * 2023-10-05 22:14:10 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-05 22:14:10 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-05 22:14:10 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-05 22:14:10 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-05 22:14:10 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-05 22:14:10 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-05 22:14:10 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-05 22:14:10 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-05 22:14:10 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-05 22:14:10 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-05 22:14:10 (4259) [INFO] * 2023-10-05 22:14:10 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-05 22:14:10 (4229) [INFO] * 2023-10-05 22:14:34 (4242) [INFO] * 2023-10-05 22:14:34 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-05 22:14:34 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-05 22:14:34 (4259) [INFO] * 2023-10-05 22:14:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-05 22:14:34 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-05 22:14:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-05 22:14:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OYpJV2YlDF/ea_profile.json * 2023-10-05 22:15:00 (2293) [INFO] Backed up EA4 profile to /tmp/OYpJV2YlDF/ea_profile.json * 2023-10-05 22:15: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-05 22:15:01 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-06 22:14:13 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-06 22:14:13 (1752) [INFO] Checking if your system is up to date: * 2023-10-06 22:14:13 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-06 22:14:13 (4229) [INFO] * 2023-10-06 22:14:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-06 22:14:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-06 22:14:14 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-06 22:14:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-06 22:14:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-06 22:14:14 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-06 22:14:14 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-06 22:14:14 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-06 22:14:14 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-06 22:14:14 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-06 22:14:14 (4259) [INFO] * 2023-10-06 22:14:14 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-06 22:14:14 (4229) [INFO] * 2023-10-06 22:14:39 (4242) [INFO] * 2023-10-06 22:14:39 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-06 22:14:39 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-06 22:14:39 (4259) [INFO] * 2023-10-06 22:14:39 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-06 22:14:39 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-06 22:15:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-06 22:15:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YD2X5QNL8D/ea_profile.json * 2023-10-06 22:15:06 (2293) [INFO] Backed up EA4 profile to /tmp/YD2X5QNL8D/ea_profile.json * 2023-10-06 22:15: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-06 22:15:07 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-07 22:15:07 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-07 22:15:07 (1752) [INFO] Checking if your system is up to date: * 2023-10-07 22:15:07 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-07 22:15:07 (4229) [INFO] * 2023-10-07 22:15:07 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-07 22:15:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-07 22:15:07 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-07 22:15:07 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-07 22:15:07 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-07 22:15:07 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-07 22:15:07 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-07 22:15:07 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-07 22:15:07 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-07 22:15:07 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-07 22:15:07 (4259) [INFO] * 2023-10-07 22:15:07 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-07 22:15:07 (4229) [INFO] * 2023-10-07 22:15:37 (4242) [INFO] * 2023-10-07 22:15:37 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-07 22:15:37 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-07 22:15:37 (4259) [INFO] * 2023-10-07 22:15:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-07 22:15:37 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-07 22:16:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-07 22:16:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SG_iI9nsHb/ea_profile.json * 2023-10-07 22:16:03 (2293) [INFO] Backed up EA4 profile to /tmp/SG_iI9nsHb/ea_profile.json * 2023-10-07 22:16:04 (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 22:16:04 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-08 22:15:08 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-08 22:15:08 (1752) [INFO] Checking if your system is up to date: * 2023-10-08 22:15:08 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-08 22:15:08 (4229) [INFO] * 2023-10-08 22:15:08 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-08 22:15:08 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-08 22:15:08 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-08 22:15:08 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-08 22:15:08 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-08 22:15:08 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-08 22:15:08 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-08 22:15:08 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-08 22:15:08 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-08 22:15:08 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-08 22:15:08 (4259) [INFO] * 2023-10-08 22:15:08 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-08 22:15:08 (4229) [INFO] * 2023-10-08 22:15:34 (4242) [INFO] * 2023-10-08 22:15:34 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-08 22:15:34 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-08 22:15:34 (4259) [INFO] * 2023-10-08 22:15:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-08 22:15:34 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-08 22:15:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-08 22:15:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sRq3qZdupm/ea_profile.json * 2023-10-08 22:15:59 (2293) [INFO] Backed up EA4 profile to /tmp/sRq3qZdupm/ea_profile.json * 2023-10-08 22:16:00 (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 22:16:00 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-09 22:14:37 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-09 22:14:37 (1752) [INFO] Checking if your system is up to date: * 2023-10-09 22:14:37 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-09 22:14:37 (4229) [INFO] * 2023-10-09 22:14:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-09 22:14:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-09 22:14:38 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-09 22:14:38 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-09 22:14:38 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-09 22:14:38 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-09 22:14:38 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-09 22:14:38 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-09 22:14:38 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-09 22:14:38 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-09 22:14:38 (4259) [INFO] * 2023-10-09 22:14:38 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-09 22:14:38 (4229) [INFO] * 2023-10-09 22:15:02 (4242) [INFO] * 2023-10-09 22:15:02 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-09 22:15:02 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-09 22:15:03 (4259) [INFO] * 2023-10-09 22:15:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-09 22:15:03 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-09 22:15:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-09 22:15:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ylwRqjyA22/ea_profile.json * 2023-10-09 22:15:31 (2293) [INFO] Backed up EA4 profile to /tmp/ylwRqjyA22/ea_profile.json * 2023-10-09 22:15: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-10-09 22:15:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-10 22:14:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-10 22:14:21 (1752) [INFO] Checking if your system is up to date: * 2023-10-10 22:14:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-10 22:14:21 (4229) [INFO] * 2023-10-10 22:14:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-10 22:14:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-10 22:14:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-10 22:14:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-10 22:14:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-10 22:14:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-10 22:14:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-10 22:14:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-10 22:14:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-10 22:14:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-10 22:14:22 (4259) [INFO] * 2023-10-10 22:14:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-10 22:14:22 (4229) [INFO] * 2023-10-10 22:14:45 (4242) [INFO] * 2023-10-10 22:14:45 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-10 22:14:45 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-10 22:14:45 (4259) [INFO] * 2023-10-10 22:14:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-10 22:14:45 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-10 22:15:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-10 22:15:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HFTptwaTQg/ea_profile.json * 2023-10-10 22:15:10 (2293) [INFO] Backed up EA4 profile to /tmp/HFTptwaTQg/ea_profile.json * 2023-10-10 22:15: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-10 22:15:11 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-11 22:14:08 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-11 22:14:08 (1752) [INFO] Checking if your system is up to date: * 2023-10-11 22:14:08 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-11 22:14:08 (4229) [INFO] * 2023-10-11 22:14:08 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-11 22:14:08 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-11 22:14:08 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-11 22:14:08 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-11 22:14:08 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-11 22:14:08 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-11 22:14:08 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-11 22:14:08 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-11 22:14:08 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-11 22:14:08 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-11 22:14:08 (4259) [INFO] * 2023-10-11 22:14:08 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-11 22:14:08 (4229) [INFO] * 2023-10-11 22:14:33 (4242) [INFO] * 2023-10-11 22:14:33 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-11 22:14:33 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-11 22:14:33 (4259) [INFO] * 2023-10-11 22:14:33 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-11 22:14:33 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-11 22:15:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-11 22:15:08 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/inm2jg5JJH/ea_profile.json * 2023-10-11 22:15:09 (2293) [INFO] Backed up EA4 profile to /tmp/inm2jg5JJH/ea_profile.json * 2023-10-11 22:15:10 (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 22:15:10 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-12 22:14:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-12 22:14:05 (1752) [INFO] Checking if your system is up to date: * 2023-10-12 22:14:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-12 22:14:05 (4229) [INFO] * 2023-10-12 22:14:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-12 22:14:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-12 22:14:05 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-12 22:14:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-12 22:14:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-12 22:14:05 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-12 22:14:05 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-12 22:14:05 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-12 22:14:05 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-12 22:14:05 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-12 22:14:05 (4259) [INFO] * 2023-10-12 22:14:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-12 22:14:05 (4229) [INFO] * 2023-10-12 22:14:29 (4242) [INFO] * 2023-10-12 22:14:29 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-12 22:14:29 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-12 22:14:29 (4259) [INFO] * 2023-10-12 22:14:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-12 22:14:29 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-12 22:14:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-12 22:14:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EH2oycEnQg/ea_profile.json * 2023-10-12 22:14:59 (2293) [INFO] Backed up EA4 profile to /tmp/EH2oycEnQg/ea_profile.json * 2023-10-12 22:15:00 (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 22:15:00 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-13 22:15:31 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-13 22:15:31 (1752) [INFO] Checking if your system is up to date: * 2023-10-13 22:15:31 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-13 22:15:31 (4229) [INFO] * 2023-10-13 22:15:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-13 22:15:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-13 22:15:31 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-13 22:15:31 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-13 22:15:31 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-13 22:15:31 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-13 22:15:31 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-13 22:15:31 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-13 22:15:31 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-13 22:15:31 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-13 22:15:31 (4259) [INFO] * 2023-10-13 22:15:31 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-13 22:15:31 (4229) [INFO] * 2023-10-13 22:15:57 (4242) [INFO] * 2023-10-13 22:15:57 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-13 22:15:57 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-13 22:15:58 (4259) [INFO] * 2023-10-13 22:15:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-13 22:15:58 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-13 22:16:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-13 22:16:22 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1RVC45SNYA/ea_profile.json * 2023-10-13 22:16:23 (2293) [INFO] Backed up EA4 profile to /tmp/1RVC45SNYA/ea_profile.json * 2023-10-13 22:16: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-13 22:16:23 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-14 22:15:06 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-14 22:15:06 (1752) [INFO] Checking if your system is up to date: * 2023-10-14 22:15:06 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-14 22:15:06 (4229) [INFO] * 2023-10-14 22:15:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-14 22:15:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-14 22:15:06 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-14 22:15:06 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-14 22:15:06 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-14 22:15:06 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-14 22:15:06 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-14 22:15:06 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-14 22:15:06 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-14 22:15:06 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-14 22:15:06 (4259) [INFO] * 2023-10-14 22:15:06 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-14 22:15:06 (4229) [INFO] * 2023-10-14 22:15:30 (4242) [INFO] * 2023-10-14 22:15:30 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-14 22:15:30 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-14 22:15:30 (4259) [INFO] * 2023-10-14 22:15:30 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-14 22:15:30 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-14 22:15:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-14 22:15:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0yMXyF7wkG/ea_profile.json * 2023-10-14 22:15:56 (2293) [INFO] Backed up EA4 profile to /tmp/0yMXyF7wkG/ea_profile.json * 2023-10-14 22:15: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-14 22:15:57 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-15 22:15:01 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-15 22:15:01 (1752) [INFO] Checking if your system is up to date: * 2023-10-15 22:15:01 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-15 22:15:01 (4229) [INFO] * 2023-10-15 22:15:02 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-15 22:15:02 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-15 22:15:02 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-15 22:15:02 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-15 22:15:02 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-15 22:15:02 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-15 22:15:02 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-15 22:15:02 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-15 22:15:02 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-15 22:15:02 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-15 22:15:02 (4259) [INFO] * 2023-10-15 22:15:02 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-15 22:15:02 (4229) [INFO] * 2023-10-15 22:15:27 (4242) [INFO] * 2023-10-15 22:15:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-15 22:15:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-15 22:15:28 (4259) [INFO] * 2023-10-15 22:15:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-15 22:15:28 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-15 22:15:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-15 22:15:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Cbgc9yI02V/ea_profile.json * 2023-10-15 22:15:53 (2293) [INFO] Backed up EA4 profile to /tmp/Cbgc9yI02V/ea_profile.json * 2023-10-15 22:15: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-15 22:15:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-16 22:14:18 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-16 22:14:18 (1752) [INFO] Checking if your system is up to date: * 2023-10-16 22:14:18 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-16 22:14:18 (4229) [INFO] * 2023-10-16 22:14:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-16 22:14:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-16 22:14:18 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-16 22:14:18 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-16 22:14:18 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-16 22:14:18 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-16 22:14:18 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-16 22:14:18 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-16 22:14:18 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-16 22:14:18 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-16 22:14:18 (4259) [INFO] * 2023-10-16 22:14:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-16 22:14:18 (4229) [INFO] * 2023-10-16 22:14:41 (4242) [INFO] * 2023-10-16 22:14:41 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-16 22:14:41 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-16 22:14:41 (4259) [INFO] * 2023-10-16 22:14:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-16 22:14:41 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-16 22:15:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-16 22:15:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8lkBiKqEn6/ea_profile.json * 2023-10-16 22:15:10 (2293) [INFO] Backed up EA4 profile to /tmp/8lkBiKqEn6/ea_profile.json * 2023-10-16 22:15: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-16 22:15:11 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-17 22:14:04 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-17 22:14:04 (1752) [INFO] Checking if your system is up to date: * 2023-10-17 22:14:04 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-17 22:14:04 (4229) [INFO] * 2023-10-17 22:14:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-17 22:14:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-17 22:14:04 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-17 22:14:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-17 22:14:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-17 22:14:04 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-17 22:14:04 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-17 22:14:04 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-17 22:14:04 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-17 22:14:04 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-17 22:14:04 (4259) [INFO] * 2023-10-17 22:14:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-17 22:14:04 (4229) [INFO] * 2023-10-17 22:14:26 (4242) [INFO] * 2023-10-17 22:14:26 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-17 22:14:26 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-17 22:14:27 (4259) [INFO] * 2023-10-17 22:14:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-17 22:14:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-17 22:14:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-17 22:14:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aqvgi2eMhG/ea_profile.json * 2023-10-17 22:14:53 (2293) [INFO] Backed up EA4 profile to /tmp/aqvgi2eMhG/ea_profile.json * 2023-10-17 22:14: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-17 22:14:54 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-18 22:14:43 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-18 22:14:43 (1752) [INFO] Checking if your system is up to date: * 2023-10-18 22:14:43 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-18 22:14:43 (4229) [INFO] * 2023-10-18 22:14:43 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-18 22:14:43 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-18 22:14:43 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-18 22:14:43 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-18 22:14:43 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-18 22:14:43 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-18 22:14:43 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-18 22:14:43 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-18 22:14:43 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-18 22:14:43 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-18 22:14:43 (4259) [INFO] * 2023-10-18 22:14:43 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-18 22:14:43 (4229) [INFO] * 2023-10-18 22:15:07 (4242) [INFO] * 2023-10-18 22:15:07 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-18 22:15:07 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-18 22:15:07 (4259) [INFO] * 2023-10-18 22:15:07 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-18 22:15:07 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-18 22:15:32 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-18 22:15:32 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EghKrI_vYD/ea_profile.json * 2023-10-18 22:15:33 (2293) [INFO] Backed up EA4 profile to /tmp/EghKrI_vYD/ea_profile.json * 2023-10-18 22:15: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-10-18 22:15:34 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-19 22:14:54 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-19 22:14:54 (1752) [INFO] Checking if your system is up to date: * 2023-10-19 22:14:54 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-19 22:14:54 (4229) [INFO] * 2023-10-19 22:14:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-19 22:14:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-19 22:14:54 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-19 22:14:54 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-19 22:14:54 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-19 22:14:54 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-19 22:14:54 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-19 22:14:54 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-19 22:14:54 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-19 22:14:54 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-19 22:14:54 (4259) [INFO] * 2023-10-19 22:14:54 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-19 22:14:54 (4229) [INFO] * 2023-10-19 22:15:17 (4242) [INFO] * 2023-10-19 22:15:17 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-19 22:15:17 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-19 22:15:17 (4259) [INFO] * 2023-10-19 22:15:17 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-19 22:15:17 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-19 22:15:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-19 22:15:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o_zF2kqKLt/ea_profile.json * 2023-10-19 22:15:44 (2293) [INFO] Backed up EA4 profile to /tmp/o_zF2kqKLt/ea_profile.json * 2023-10-19 22:15: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-19 22:15:45 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-20 22:14:03 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-20 22:14:03 (1752) [INFO] Checking if your system is up to date: * 2023-10-20 22:14:03 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-20 22:14:03 (4229) [INFO] * 2023-10-20 22:14:03 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-20 22:14:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-20 22:14:04 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-20 22:14:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-20 22:14:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-20 22:14:04 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-20 22:14:04 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-20 22:14:04 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-20 22:14:04 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-20 22:14:04 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-20 22:14:04 (4259) [INFO] * 2023-10-20 22:14:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-20 22:14:04 (4229) [INFO] * 2023-10-20 22:14:28 (4242) [INFO] * 2023-10-20 22:14:28 (4242) [INFO] kernel.x86_64 3.10.0-1160.99.1.el7 updates * 2023-10-20 22:14:28 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-20 22:14:28 (4259) [INFO] * 2023-10-20 22:14:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-20 22:14:28 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-20 22:15:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-20 22:15:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yXVnLuplmO/ea_profile.json * 2023-10-20 22:15:01 (2293) [INFO] Backed up EA4 profile to /tmp/yXVnLuplmO/ea_profile.json * 2023-10-20 22:15: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-20 22:15:03 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-21 22:16:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-21 22:16:14 (1752) [INFO] Checking if your system is up to date: * 2023-10-21 22:16:14 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-21 22:16:14 (4229) [INFO] * 2023-10-21 22:16:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-21 22:16:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-21 22:16:14 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-21 22:16:14 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-21 22:16:14 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-21 22:16:14 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-21 22:16:14 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-21 22:16:14 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-21 22:16:14 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-21 22:16:14 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-21 22:16:14 (4259) [INFO] * 2023-10-21 22:16:14 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-21 22:16:14 (4229) [INFO] * 2023-10-21 22:16:38 (4242) [INFO] * 2023-10-21 22:16:38 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-21 22:16:38 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-21 22:16:38 (4259) [INFO] * 2023-10-21 22:16:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-21 22:16:38 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-21 22:17:01 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-21 22:17:01 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NRgHTy__SH/ea_profile.json * 2023-10-21 22:17:02 (2293) [INFO] Backed up EA4 profile to /tmp/NRgHTy__SH/ea_profile.json * 2023-10-21 22:17: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-21 22:17:03 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-22 22:15:12 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-22 22:15:12 (1752) [INFO] Checking if your system is up to date: * 2023-10-22 22:15:12 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-22 22:15:12 (4229) [INFO] * 2023-10-22 22:15:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-22 22:15:12 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-22 22:15:12 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-22 22:15:12 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-22 22:15:12 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-22 22:15:12 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-22 22:15:12 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-22 22:15:12 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-22 22:15:13 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-22 22:15:13 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-22 22:15:13 (4259) [INFO] * 2023-10-22 22:15:13 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-22 22:15:13 (4229) [INFO] * 2023-10-22 22:15:51 (4242) [INFO] * 2023-10-22 22:15:51 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-22 22:15:51 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-22 22:15:51 (4259) [INFO] * 2023-10-22 22:15:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-22 22:15:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-22 22:16:17 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-22 22:16:17 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oMO9nXtSi1/ea_profile.json * 2023-10-22 22:16:17 (2293) [INFO] Backed up EA4 profile to /tmp/oMO9nXtSi1/ea_profile.json * 2023-10-22 22:16:18 (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 22:16:18 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-23 22:14:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-23 22:14:22 (1752) [INFO] Checking if your system is up to date: * 2023-10-23 22:14:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-23 22:14:22 (4229) [INFO] * 2023-10-23 22:14:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-23 22:14:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-23 22:14:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-23 22:14:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-23 22:14:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-23 22:14:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-23 22:14:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-23 22:14:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-23 22:14:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-23 22:14:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-23 22:14:22 (4259) [INFO] * 2023-10-23 22:14:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-23 22:14:22 (4229) [INFO] * 2023-10-23 22:14:46 (4242) [INFO] * 2023-10-23 22:14:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-23 22:14:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-23 22:14:46 (4259) [INFO] * 2023-10-23 22:14:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-23 22:14:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-23 22:15:13 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-23 22:15:13 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZmzI0TFreB/ea_profile.json * 2023-10-23 22:15:14 (2293) [INFO] Backed up EA4 profile to /tmp/ZmzI0TFreB/ea_profile.json * 2023-10-23 22:15:15 (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 22:15:15 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-24 22:15:45 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-24 22:15:45 (1752) [INFO] Checking if your system is up to date: * 2023-10-24 22:15:45 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-24 22:15:45 (4229) [INFO] * 2023-10-24 22:15:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-24 22:15:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-24 22:15:45 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-24 22:15:45 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-24 22:15:45 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-24 22:15:45 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-24 22:15:45 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-24 22:15:45 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-24 22:15:46 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-24 22:15:46 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-24 22:15:46 (4259) [INFO] * 2023-10-24 22:15:46 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-24 22:15:46 (4229) [INFO] * 2023-10-24 22:16:19 (4242) [INFO] * 2023-10-24 22:16:19 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-24 22:16:19 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-24 22:16:19 (4259) [INFO] * 2023-10-24 22:16:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-24 22:16:19 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-24 22:16:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-24 22:16:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/12x9MnPi6Y/ea_profile.json * 2023-10-24 22:16:43 (2293) [INFO] Backed up EA4 profile to /tmp/12x9MnPi6Y/ea_profile.json * 2023-10-24 22:16: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-24 22:16:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-25 22:14:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-25 22:14:21 (1752) [INFO] Checking if your system is up to date: * 2023-10-25 22:14:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-25 22:14:21 (4229) [INFO] * 2023-10-25 22:14:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-25 22:14:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-25 22:14:21 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-25 22:14:21 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-25 22:14:21 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-25 22:14:21 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-25 22:14:21 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-25 22:14:21 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-25 22:14:21 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-25 22:14:21 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-25 22:14:21 (4259) [INFO] * 2023-10-25 22:14:21 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-25 22:14:21 (4229) [INFO] * 2023-10-25 22:14:46 (4242) [INFO] * 2023-10-25 22:14:46 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-25 22:14:46 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-25 22:14:46 (4259) [INFO] * 2023-10-25 22:14:46 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-25 22:14:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-25 22:15:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-25 22:15:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PMtKFJT2Z3/ea_profile.json * 2023-10-25 22:15:12 (2293) [INFO] Backed up EA4 profile to /tmp/PMtKFJT2Z3/ea_profile.json * 2023-10-25 22:15: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-25 22:15:14 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-26 22:15:53 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-26 22:15:53 (1752) [INFO] Checking if your system is up to date: * 2023-10-26 22:15:53 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-26 22:15:53 (4229) [INFO] * 2023-10-26 22:15:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-26 22:15:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-26 22:15:54 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-26 22:15:54 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-26 22:15:54 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-26 22:15:54 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-26 22:15:54 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-26 22:15:54 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-26 22:15:54 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-26 22:15:54 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-26 22:15:54 (4259) [INFO] * 2023-10-26 22:15:54 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-26 22:15:54 (4229) [INFO] * 2023-10-26 22:16:27 (4242) [INFO] * 2023-10-26 22:16:27 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-26 22:16:27 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-26 22:16:27 (4259) [INFO] * 2023-10-26 22:16:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-26 22:16:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-26 22:16:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-26 22:17:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LcDVuPb2ty/ea_profile.json * 2023-10-26 22:17:01 (2293) [INFO] Backed up EA4 profile to /tmp/LcDVuPb2ty/ea_profile.json * 2023-10-26 22:17: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-26 22:17:03 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-27 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-27 22:15:27 (1752) [INFO] Checking if your system is up to date: * 2023-10-27 22:15:27 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-27 22:15:27 (4229) [INFO] * 2023-10-27 22:15:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-27 22:15:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-27 22:15:28 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-27 22:15:28 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-27 22:15:28 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-27 22:15:28 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-27 22:15:28 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-27 22:15:28 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-27 22:15:29 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-27 22:15:29 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-27 22:15:29 (4259) [INFO] * 2023-10-27 22:15:29 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-27 22:15:29 (4229) [INFO] * 2023-10-27 22:16:13 (4242) [INFO] * 2023-10-27 22:16:13 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-27 22:16:13 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-27 22:16:13 (4259) [INFO] * 2023-10-27 22:16:13 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-27 22:16:13 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-27 22:16:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-27 22:16:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/u7VlhALrJs/ea_profile.json * 2023-10-27 22:16:43 (2293) [INFO] Backed up EA4 profile to /tmp/u7VlhALrJs/ea_profile.json * 2023-10-27 22:16: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-27 22:16:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-28 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-28 22:15:27 (1752) [INFO] Checking if your system is up to date: * 2023-10-28 22:15:27 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-28 22:15:27 (4229) [INFO] * 2023-10-28 22:15:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-28 22:15:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-28 22:15:28 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-28 22:15:28 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-28 22:15:28 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-28 22:15:28 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-28 22:15:28 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-28 22:15:28 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-28 22:15:28 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-28 22:15:28 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-28 22:15:28 (4259) [INFO] * 2023-10-28 22:15:28 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-28 22:15:28 (4229) [INFO] * 2023-10-28 22:16:01 (4242) [INFO] * 2023-10-28 22:16:01 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-28 22:16:01 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-28 22:16:02 (4259) [INFO] * 2023-10-28 22:16:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-28 22:16:02 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-28 22:16:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-28 22:16:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B515KbvwHL/ea_profile.json * 2023-10-28 22:16:34 (2293) [INFO] Backed up EA4 profile to /tmp/B515KbvwHL/ea_profile.json * 2023-10-28 22:16: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-10-28 22:16:35 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-29 22:15:28 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-29 22:15:28 (1752) [INFO] Checking if your system is up to date: * 2023-10-29 22:15:28 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-29 22:15:28 (4229) [INFO] * 2023-10-29 22:15:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-29 22:15:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-29 22:15:29 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-29 22:15:29 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-29 22:15:29 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-29 22:15:29 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-29 22:15:29 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-29 22:15:29 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-29 22:15:29 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-29 22:15:29 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-29 22:15:29 (4259) [INFO] * 2023-10-29 22:15:29 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-29 22:15:29 (4229) [INFO] * 2023-10-29 22:16:14 (4242) [INFO] * 2023-10-29 22:16:14 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-29 22:16:14 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-29 22:16:14 (4259) [INFO] * 2023-10-29 22:16:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-29 22:16:14 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-29 22:16:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-29 22:16:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/m_BHIgexmG/ea_profile.json * 2023-10-29 22:16:50 (2293) [INFO] Backed up EA4 profile to /tmp/m_BHIgexmG/ea_profile.json * 2023-10-29 22:16: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 22:16:51 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-30 22:14:25 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-30 22:14:25 (1752) [INFO] Checking if your system is up to date: * 2023-10-30 22:14:25 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-30 22:14:25 (4229) [INFO] * 2023-10-30 22:14:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-30 22:14:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-30 22:14:26 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-30 22:14:26 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-30 22:14:26 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-30 22:14:26 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-30 22:14:26 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-30 22:14:26 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-30 22:14:26 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-30 22:14:26 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-30 22:14:26 (4259) [INFO] * 2023-10-30 22:14:26 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-30 22:14:26 (4229) [INFO] * 2023-10-30 22:14:57 (4242) [INFO] * 2023-10-30 22:14:57 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-30 22:14:57 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-30 22:14:57 (4259) [INFO] * 2023-10-30 22:14:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-30 22:14:57 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-30 22:15:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-30 22:15:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/u6PqQ2pZWq/ea_profile.json * 2023-10-30 22:15:39 (2293) [INFO] Backed up EA4 profile to /tmp/u6PqQ2pZWq/ea_profile.json * 2023-10-30 22:15: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-10-30 22:15:40 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-10-31 22:14:45 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-10-31 22:14:45 (1752) [INFO] Checking if your system is up to date: * 2023-10-31 22:14:45 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-10-31 22:14:45 (4229) [INFO] * 2023-10-31 22:14:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-10-31 22:14:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-10-31 22:14:45 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-10-31 22:14:45 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-10-31 22:14:45 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-10-31 22:14:45 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-10-31 22:14:45 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-10-31 22:14:45 (4242) [INFO] : wp-toolkit-thirdparties * 2023-10-31 22:14:45 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-10-31 22:14:45 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-10-31 22:14:45 (4259) [INFO] * 2023-10-31 22:14:45 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-10-31 22:14:45 (4229) [INFO] * 2023-10-31 22:15:21 (4242) [INFO] * 2023-10-31 22:15:21 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-10-31 22:15:21 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-10-31 22:15:22 (4259) [INFO] * 2023-10-31 22:15:22 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-10-31 22:15:22 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-10-31 22:15:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-10-31 22:15:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Ah6SVWc5Nj/ea_profile.json * 2023-10-31 22:15:55 (2293) [INFO] Backed up EA4 profile to /tmp/Ah6SVWc5Nj/ea_profile.json * 2023-10-31 22:15:56 (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 22:15:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-01 22:15:05 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-01 22:15:05 (1752) [INFO] Checking if your system is up to date: * 2023-11-01 22:15:05 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-01 22:15:05 (4229) [INFO] * 2023-11-01 22:15:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-01 22:15:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-01 22:15:05 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-01 22:15:05 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-01 22:15:05 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-01 22:15:05 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-01 22:15:05 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-01 22:15:05 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-01 22:15:05 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-01 22:15:05 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-01 22:15:05 (4259) [INFO] * 2023-11-01 22:15:05 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-01 22:15:05 (4229) [INFO] * 2023-11-01 22:15:41 (4242) [INFO] * 2023-11-01 22:15:41 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-01 22:15:41 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-01 22:15:41 (4259) [INFO] * 2023-11-01 22:15:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-01 22:15:41 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-01 22:16:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-01 22:16:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fEjrV5XW9N/ea_profile.json * 2023-11-01 22:16:17 (2293) [INFO] Backed up EA4 profile to /tmp/fEjrV5XW9N/ea_profile.json * 2023-11-01 22:16:18 (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 22:16:18 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-02 22:14:34 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-02 22:14:35 (1752) [INFO] Checking if your system is up to date: * 2023-11-02 22:14:35 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-02 22:14:35 (4229) [INFO] * 2023-11-02 22:14:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-02 22:14:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-02 22:14:35 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-02 22:14:35 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-02 22:14:35 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-02 22:14:35 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-02 22:14:35 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-02 22:14:35 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-02 22:14:35 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-02 22:14:35 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-02 22:14:35 (4259) [INFO] * 2023-11-02 22:14:35 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-02 22:14:35 (4229) [INFO] * 2023-11-02 22:15:19 (4242) [INFO] * 2023-11-02 22:15:19 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-02 22:15:19 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-02 22:15:19 (4259) [INFO] * 2023-11-02 22:15:19 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-02 22:15:19 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-02 22:15:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-02 22:15:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yHKqvF1hVJ/ea_profile.json * 2023-11-02 22:15:51 (2293) [INFO] Backed up EA4 profile to /tmp/yHKqvF1hVJ/ea_profile.json * 2023-11-02 22:15: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-02 22:15:56 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-03 22:14:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-03 22:14:19 (1752) [INFO] Checking if your system is up to date: * 2023-11-03 22:14:19 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-03 22:14:19 (4229) [INFO] * 2023-11-03 22:14:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-03 22:14:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-03 22:14:19 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-03 22:14:19 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-03 22:14:19 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-03 22:14:19 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-03 22:14:19 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-03 22:14:19 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-03 22:14:19 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-03 22:14:19 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-03 22:14:19 (4259) [INFO] * 2023-11-03 22:14:19 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-03 22:14:19 (4229) [INFO] * 2023-11-03 22:14:50 (4242) [INFO] * 2023-11-03 22:14:50 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-03 22:14:50 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-03 22:14:50 (4259) [INFO] * 2023-11-03 22:14:50 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-03 22:14:50 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-03 22:15:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-03 22:15:25 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KXpTEVfoK3/ea_profile.json * 2023-11-03 22:15:27 (2293) [INFO] Backed up EA4 profile to /tmp/KXpTEVfoK3/ea_profile.json * 2023-11-03 22:15: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-03 22:15:28 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-04 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-04 22:15:27 (1752) [INFO] Checking if your system is up to date: * 2023-11-04 22:15:27 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-04 22:15:27 (4229) [INFO] * 2023-11-04 22:15:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-04 22:15:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-04 22:15:27 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-04 22:15:27 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-04 22:15:27 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-04 22:15:27 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-04 22:15:27 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-04 22:15:27 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-04 22:15:28 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-04 22:15:28 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-04 22:15:28 (4259) [INFO] * 2023-11-04 22:15:28 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-04 22:15:28 (4229) [INFO] * 2023-11-04 22:15:59 (4242) [INFO] * 2023-11-04 22:15:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-04 22:15:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-04 22:15:59 (4259) [INFO] * 2023-11-04 22:15:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-04 22:15:59 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-04 22:16:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-04 22:16:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L8YPGos44z/ea_profile.json * 2023-11-04 22:16:29 (2293) [INFO] Backed up EA4 profile to /tmp/L8YPGos44z/ea_profile.json * 2023-11-04 22:16: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-11-04 22:16:31 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-05 22:15:15 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-05 22:15:15 (1752) [INFO] Checking if your system is up to date: * 2023-11-05 22:15:15 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-05 22:15:15 (4229) [INFO] * 2023-11-05 22:15:15 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-05 22:15:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-05 22:15:15 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-05 22:15:15 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-05 22:15:15 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-05 22:15:15 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-05 22:15:15 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-05 22:15:15 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-05 22:15:15 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-05 22:15:15 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-05 22:15:15 (4259) [INFO] * 2023-11-05 22:15:15 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-05 22:15:15 (4229) [INFO] * 2023-11-05 22:15:48 (4242) [INFO] * 2023-11-05 22:15:48 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-05 22:15:48 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-05 22:15:48 (4259) [INFO] * 2023-11-05 22:15:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-05 22:15:48 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-05 22:16:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-05 22:16:19 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WJ2Kek5xhV/ea_profile.json * 2023-11-05 22:16:20 (2293) [INFO] Backed up EA4 profile to /tmp/WJ2Kek5xhV/ea_profile.json * 2023-11-05 22:16:21 (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 22:16:21 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-06 22:14:16 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-06 22:14:16 (1752) [INFO] Checking if your system is up to date: * 2023-11-06 22:14:16 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-06 22:14:16 (4229) [INFO] * 2023-11-06 22:14:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-06 22:14:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-06 22:14:16 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-06 22:14:16 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-06 22:14:16 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-06 22:14:16 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-06 22:14:16 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-06 22:14:16 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-06 22:14:17 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-06 22:14:17 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-06 22:14:17 (4259) [INFO] * 2023-11-06 22:14:17 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-06 22:14:17 (4229) [INFO] * 2023-11-06 22:14:48 (4242) [INFO] * 2023-11-06 22:14:48 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-06 22:14:48 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-06 22:14:48 (4259) [INFO] * 2023-11-06 22:14:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-06 22:14:48 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-06 22:15:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-06 22:15:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iurooaY8aR/ea_profile.json * 2023-11-06 22:15:21 (2293) [INFO] Backed up EA4 profile to /tmp/iurooaY8aR/ea_profile.json * 2023-11-06 22:15: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-11-06 22:15:22 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-07 22:14:23 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-07 22:14:23 (1752) [INFO] Checking if your system is up to date: * 2023-11-07 22:14:23 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-07 22:14:23 (4229) [INFO] * 2023-11-07 22:14:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-07 22:14:24 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-07 22:14:24 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-07 22:14:24 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-07 22:14:24 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-07 22:14:24 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-07 22:14:24 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-07 22:14:24 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-07 22:14:24 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-07 22:14:24 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-07 22:14:24 (4259) [INFO] * 2023-11-07 22:14:24 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-07 22:14:24 (4229) [INFO] * 2023-11-07 22:14:56 (4242) [INFO] * 2023-11-07 22:14:56 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-07 22:14:56 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-07 22:14:56 (4259) [INFO] * 2023-11-07 22:14:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-07 22:14:56 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-07 22:15:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-07 22:15:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/p5AhoLrPTJ/ea_profile.json * 2023-11-07 22:15:31 (2293) [INFO] Backed up EA4 profile to /tmp/p5AhoLrPTJ/ea_profile.json * 2023-11-07 22:15: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-07 22:15:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-08 22:15:03 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-08 22:15:03 (1752) [INFO] Checking if your system is up to date: * 2023-11-08 22:15:03 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-08 22:15:03 (4229) [INFO] * 2023-11-08 22:15:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-08 22:15:04 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-08 22:15:04 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-08 22:15:04 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-08 22:15:04 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-08 22:15:04 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-08 22:15:04 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-08 22:15:04 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-08 22:15:04 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-08 22:15:04 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-08 22:15:04 (4259) [INFO] * 2023-11-08 22:15:04 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-08 22:15:04 (4229) [INFO] * 2023-11-08 22:15:37 (4242) [INFO] * 2023-11-08 22:15:37 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-08 22:15:37 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-08 22:15:37 (4259) [INFO] * 2023-11-08 22:15:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-08 22:15:38 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-08 22:16:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-08 22:16:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3jsC59WIk4/ea_profile.json * 2023-11-08 22:16:13 (2293) [INFO] Backed up EA4 profile to /tmp/3jsC59WIk4/ea_profile.json * 2023-11-08 22:16:15 (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 22:16:15 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-09 22:15:52 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-09 22:15:52 (1752) [INFO] Checking if your system is up to date: * 2023-11-09 22:15:52 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-09 22:15:52 (4229) [INFO] * 2023-11-09 22:15:52 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-09 22:15:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-09 22:15:53 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-09 22:15:53 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-09 22:15:53 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-09 22:15:53 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-09 22:15:53 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-09 22:15:53 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-09 22:15:53 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-09 22:15:53 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-09 22:15:53 (4259) [INFO] * 2023-11-09 22:15:53 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-09 22:15:53 (4229) [INFO] * 2023-11-09 22:16:22 (4242) [INFO] * 2023-11-09 22:16:22 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-09 22:16:22 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-09 22:16:22 (4259) [INFO] * 2023-11-09 22:16:22 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-09 22:16:22 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-09 22:16:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-09 22:16:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2NOoVs1NoB/ea_profile.json * 2023-11-09 22:16:52 (2293) [INFO] Backed up EA4 profile to /tmp/2NOoVs1NoB/ea_profile.json * 2023-11-09 22:16: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-09 22:16:53 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-10 22:14:20 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-10 22:14:20 (1752) [INFO] Checking if your system is up to date: * 2023-11-10 22:14:20 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-10 22:14:20 (4229) [INFO] * 2023-11-10 22:14:20 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-10 22:14:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-10 22:14:20 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-10 22:14:20 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-10 22:14:20 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-10 22:14:20 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-10 22:14:20 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-10 22:14:20 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-10 22:14:20 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-10 22:14:20 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-10 22:14:20 (4259) [INFO] * 2023-11-10 22:14:20 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-10 22:14:20 (4229) [INFO] * 2023-11-10 22:14:50 (4242) [INFO] * 2023-11-10 22:14:50 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-10 22:14:50 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-10 22:14:51 (4259) [INFO] * 2023-11-10 22:14:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-10 22:14:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-10 22:15:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-10 22:15:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7W9EDaBuYA/ea_profile.json * 2023-11-10 22:15:21 (2293) [INFO] Backed up EA4 profile to /tmp/7W9EDaBuYA/ea_profile.json * 2023-11-10 22:15: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-11-10 22:15:22 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-11 22:15:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-11 22:15:22 (1752) [INFO] Checking if your system is up to date: * 2023-11-11 22:15:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-11 22:15:22 (4229) [INFO] * 2023-11-11 22:15:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-11 22:15:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-11 22:15:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-11 22:15:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-11 22:15:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-11 22:15:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-11 22:15:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-11 22:15:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-11 22:15:23 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-11 22:15:23 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-11 22:15:23 (4259) [INFO] * 2023-11-11 22:15:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-11 22:15:23 (4229) [INFO] * 2023-11-11 22:15:55 (4242) [INFO] * 2023-11-11 22:15:55 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-11 22:15:55 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-11 22:15:55 (4259) [INFO] * 2023-11-11 22:15:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-11 22:15:55 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-11 22:16:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-11 22:16:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q61t_0HsN2/ea_profile.json * 2023-11-11 22:16:27 (2293) [INFO] Backed up EA4 profile to /tmp/q61t_0HsN2/ea_profile.json * 2023-11-11 22:16: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-11-11 22:16:31 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-12 22:15:27 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-12 22:15:27 (1752) [INFO] Checking if your system is up to date: * 2023-11-12 22:15:27 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-12 22:15:27 (4229) [INFO] * 2023-11-12 22:15:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-12 22:15:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-12 22:15:27 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-12 22:15:27 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-12 22:15:27 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-12 22:15:27 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-12 22:15:27 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-12 22:15:27 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-12 22:15:28 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-12 22:15:28 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-12 22:15:28 (4259) [INFO] * 2023-11-12 22:15:28 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-12 22:15:28 (4229) [INFO] * 2023-11-12 22:16:00 (4242) [INFO] * 2023-11-12 22:16:00 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-12 22:16:00 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-12 22:16:00 (4259) [INFO] * 2023-11-12 22:16:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-12 22:16:00 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-12 22:16:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-12 22:16:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9WPhWReDFU/ea_profile.json * 2023-11-12 22:16:33 (2293) [INFO] Backed up EA4 profile to /tmp/9WPhWReDFU/ea_profile.json * 2023-11-12 22:16:37 (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 22:16:37 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-13 22:14:17 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-13 22:14:17 (1752) [INFO] Checking if your system is up to date: * 2023-11-13 22:14:17 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-13 22:14:17 (4229) [INFO] * 2023-11-13 22:14:17 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-13 22:14:17 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-13 22:14:17 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-13 22:14:17 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-13 22:14:17 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-13 22:14:17 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-13 22:14:17 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-13 22:14:17 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-13 22:14:17 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-13 22:14:17 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-13 22:14:18 (4259) [INFO] * 2023-11-13 22:14:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-13 22:14:18 (4229) [INFO] * 2023-11-13 22:14:49 (4242) [INFO] * 2023-11-13 22:14:49 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-13 22:14:49 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-13 22:14:49 (4259) [INFO] * 2023-11-13 22:14:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-13 22:14:49 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-13 22:15:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-13 22:15:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dyIWRw5ChR/ea_profile.json * 2023-11-13 22:15:22 (2293) [INFO] Backed up EA4 profile to /tmp/dyIWRw5ChR/ea_profile.json * 2023-11-13 22:15: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-11-13 22:15:23 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-14 22:15:17 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-14 22:15:17 (1752) [INFO] Checking if your system is up to date: * 2023-11-14 22:15:17 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-14 22:15:17 (4229) [INFO] * 2023-11-14 22:15:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-14 22:15:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-14 22:15:18 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-14 22:15:18 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-14 22:15:18 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-14 22:15:18 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-14 22:15:18 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-14 22:15:18 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-14 22:15:18 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-14 22:15:18 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-14 22:15:18 (4259) [INFO] * 2023-11-14 22:15:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-14 22:15:18 (4229) [INFO] * 2023-11-14 22:16:02 (4242) [INFO] * 2023-11-14 22:16:02 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-14 22:16:02 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-14 22:16:02 (4259) [INFO] * 2023-11-14 22:16:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-14 22:16:02 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-14 22:16:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-14 22:16:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/J8MqVw_vwF/ea_profile.json * 2023-11-14 22:16:31 (2293) [INFO] Backed up EA4 profile to /tmp/J8MqVw_vwF/ea_profile.json * 2023-11-14 22:16: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-14 22:16:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-15 22:15:53 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-15 22:15:53 (1752) [INFO] Checking if your system is up to date: * 2023-11-15 22:15:53 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-15 22:15:53 (4229) [INFO] * 2023-11-15 22:15:53 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-15 22:15:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-15 22:15:53 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-15 22:15:53 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-15 22:15:53 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-15 22:15:53 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-15 22:15:53 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-15 22:15:53 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-15 22:15:53 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-15 22:15:53 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-15 22:15:53 (4259) [INFO] * 2023-11-15 22:15:53 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-15 22:15:53 (4229) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] One of the configured repositories failed (Unknown), * 2023-11-15 22:15:55 (4242) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2023-11-15 22:15:55 (4242) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2023-11-15 22:15:55 (4242) [INFO] upstream. This is most often useful if you are using a newer * 2023-11-15 22:15:55 (4242) [INFO] distribution release than is supported by the repository (and the * 2023-11-15 22:15:55 (4242) [INFO] packages for the previous distribution release still work). * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] 3. Run the command with the repository temporarily disabled * 2023-11-15 22:15:55 (4242) [INFO] yum --disablerepo= ... * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2023-11-15 22:15:55 (4242) [INFO] will then just ignore the repository until you permanently enable it * 2023-11-15 22:15:55 (4242) [INFO] again or use --enablerepo for temporary usage: * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] yum-config-manager --disable * 2023-11-15 22:15:55 (4242) [INFO] or * 2023-11-15 22:15:55 (4242) [INFO] subscription-manager repos --disable= * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2023-11-15 22:15:55 (4242) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2023-11-15 22:15:55 (4242) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2023-11-15 22:15:55 (4242) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2023-11-15 22:15:55 (4242) [INFO] compromise: * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2023-11-15 22:15:55 (4242) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-15 22:15:55 (4259) [INFO] * 2023-11-15 22:15:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-15 22:15:55 (1773) [INFO] Checking /scripts/sysup * 2023-11-15 22:15:55 (4228) [INFO] Running: /scripts/sysup * 2023-11-15 22:15:55 (4229) [INFO] * 2023-11-15 22:15:55 (4242) [INFO] checkyum version 22.3 (excludes: bind-chroot) * 2023-11-15 22:15:57 (4242) [INFO] All Needed Packages are already installed. * 2023-11-15 22:15:57 (4259) [INFO] * 2023-11-15 22:15:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-15 22:15:59 (1619) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again * 2023-11-15 22:15:59 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-15 22:15:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-15 22:15:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xZjsoBcgA2/ea_profile.json * 2023-11-15 22:16:02 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xZjsoBcgA2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272. * 2023-11-15 22:16:02 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-16 22:14:20 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-16 22:14:20 (1752) [INFO] Checking if your system is up to date: * 2023-11-16 22:14:20 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-16 22:14:20 (4229) [INFO] * 2023-11-16 22:14:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-16 22:14:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-16 22:14:21 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-16 22:14:21 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-16 22:14:21 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-16 22:14:21 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-16 22:14:21 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-16 22:14:21 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-16 22:14:21 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-16 22:14:21 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-16 22:14:21 (4259) [INFO] * 2023-11-16 22:14:21 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-16 22:14:21 (4229) [INFO] * 2023-11-16 22:14:52 (4242) [INFO] * 2023-11-16 22:14:52 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-16 22:14:52 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-16 22:14:52 (4259) [INFO] * 2023-11-16 22:14:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-16 22:14:52 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-16 22:15:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-16 22:15:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VTI4_LYxKV/ea_profile.json * 2023-11-16 22:15:27 (2293) [INFO] Backed up EA4 profile to /tmp/VTI4_LYxKV/ea_profile.json * 2023-11-16 22:15: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-16 22:15:28 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-17 22:14:35 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-17 22:14:35 (1752) [INFO] Checking if your system is up to date: * 2023-11-17 22:14:35 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-17 22:14:35 (4229) [INFO] * 2023-11-17 22:14:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-17 22:14:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-17 22:14:35 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-17 22:14:35 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-17 22:14:35 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-17 22:14:35 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-17 22:14:35 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-17 22:14:35 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-17 22:14:36 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-17 22:14:36 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-17 22:14:36 (4259) [INFO] * 2023-11-17 22:14:36 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-17 22:14:36 (4229) [INFO] * 2023-11-17 22:15:24 (4242) [INFO] * 2023-11-17 22:15:24 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-17 22:15:24 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-17 22:15:24 (4259) [INFO] * 2023-11-17 22:15:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-17 22:15:24 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-17 22:15:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-17 22:15:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e4hHjiokJt/ea_profile.json * 2023-11-17 22:15:57 (2293) [INFO] Backed up EA4 profile to /tmp/e4hHjiokJt/ea_profile.json * 2023-11-17 22:15: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-17 22:15:58 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-18 22:15:34 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-18 22:15:34 (1752) [INFO] Checking if your system is up to date: * 2023-11-18 22:15:34 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-18 22:15:34 (4229) [INFO] * 2023-11-18 22:15:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-18 22:15:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-18 22:15:35 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-18 22:15:35 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-18 22:15:35 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-18 22:15:35 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-18 22:15:35 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-18 22:15:35 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-18 22:15:35 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-18 22:15:35 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-18 22:15:35 (4259) [INFO] * 2023-11-18 22:15:35 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-18 22:15:35 (4229) [INFO] * 2023-11-18 22:16:09 (4242) [INFO] * 2023-11-18 22:16:09 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-18 22:16:09 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-18 22:16:09 (4259) [INFO] * 2023-11-18 22:16:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-18 22:16:09 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-18 22:16:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-18 22:16:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aUvJPFuTqq/ea_profile.json * 2023-11-18 22:16:38 (2293) [INFO] Backed up EA4 profile to /tmp/aUvJPFuTqq/ea_profile.json * 2023-11-18 22:16: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-18 22:16:39 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-19 22:15:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-19 22:15:14 (1752) [INFO] Checking if your system is up to date: * 2023-11-19 22:15:14 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-19 22:15:14 (4229) [INFO] * 2023-11-19 22:15:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-19 22:15:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-19 22:15:15 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-19 22:15:15 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-19 22:15:15 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-19 22:15:15 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-19 22:15:15 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-19 22:15:15 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-19 22:15:15 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-19 22:15:15 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-19 22:15:15 (4259) [INFO] * 2023-11-19 22:15:15 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-19 22:15:15 (4229) [INFO] * 2023-11-19 22:15:47 (4242) [INFO] * 2023-11-19 22:15:47 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-19 22:15:47 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-19 22:15:47 (4259) [INFO] * 2023-11-19 22:15:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-19 22:15:47 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-19 22:16:15 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-19 22:16:15 (1619) [ERROR] http://centos.mirrors.ovh.net/ftp.centos.org/7/os/x86_64/repodata/ecaab5cc3b9c10fefe6be2ecbf6f9fcb437231dac3e82cab8d9d2cf70e99644d-other.sqlite.bz2: [Errno 14] curl#56 - "Recv failure: Connection reset by peer" Trying other mirror. One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true base: Check uncompressed DB failed * 2023-11-19 22:16:15 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-19 22:16:15 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-19 22:16:15 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gzklm7zqvx/ea_profile.json * 2023-11-19 22:16:19 (2293) [INFO] Backed up EA4 profile to /tmp/gzklm7zqvx/ea_profile.json * 2023-11-19 22:16: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-11-19 22:16:20 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-20 22:14:29 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-20 22:14:29 (1752) [INFO] Checking if your system is up to date: * 2023-11-20 22:14:29 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-20 22:14:29 (4229) [INFO] * 2023-11-20 22:14:29 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-20 22:14:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-20 22:14:29 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-20 22:14:29 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-20 22:14:29 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-20 22:14:29 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-20 22:14:29 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-20 22:14:29 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-20 22:14:29 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-20 22:14:29 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-20 22:14:29 (4259) [INFO] * 2023-11-20 22:14:29 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-20 22:14:29 (4229) [INFO] * 2023-11-20 22:15:09 (4242) [INFO] * 2023-11-20 22:15:09 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-20 22:15:09 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-20 22:15:09 (4259) [INFO] * 2023-11-20 22:15:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-20 22:15:09 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-20 22:15:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-20 22:15:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bpPhE3XRCF/ea_profile.json * 2023-11-20 22:15:43 (2293) [INFO] Backed up EA4 profile to /tmp/bpPhE3XRCF/ea_profile.json * 2023-11-20 22:15: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-11-20 22:15:44 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-21 22:14:49 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-21 22:14:49 (1752) [INFO] Checking if your system is up to date: * 2023-11-21 22:14:49 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-21 22:14:49 (4229) [INFO] * 2023-11-21 22:14:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-21 22:14:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-21 22:14:50 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-21 22:14:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-21 22:14:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-21 22:14:50 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-21 22:14:50 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-21 22:14:50 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-21 22:14:50 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-21 22:14:50 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-21 22:14:50 (4259) [INFO] * 2023-11-21 22:14:50 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-21 22:14:50 (4229) [INFO] * 2023-11-21 22:15:49 (4242) [INFO] * 2023-11-21 22:15:49 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-21 22:15:49 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-21 22:15:50 (4259) [INFO] * 2023-11-21 22:15:50 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-21 22:15:50 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-21 22:17:06 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-21 22:17:06 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HaLv5x6wsI/ea_profile.json * 2023-11-21 22:17:07 (2293) [INFO] Backed up EA4 profile to /tmp/HaLv5x6wsI/ea_profile.json * 2023-11-21 22:17:08 (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 22:17:08 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-22 22:14:37 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-22 22:14:37 (1752) [INFO] Checking if your system is up to date: * 2023-11-22 22:14:37 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-22 22:14:37 (4229) [INFO] * 2023-11-22 22:14:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-22 22:14:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-22 22:14:37 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-22 22:14:37 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-22 22:14:37 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-22 22:14:37 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-22 22:14:37 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-22 22:14:37 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-22 22:14:37 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-22 22:14:37 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-22 22:14:37 (4259) [INFO] * 2023-11-22 22:14:37 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-22 22:14:37 (4229) [INFO] * 2023-11-22 22:15:12 (4242) [INFO] * 2023-11-22 22:15:12 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-22 22:15:12 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-22 22:15:12 (4259) [INFO] * 2023-11-22 22:15:12 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-22 22:15:12 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-22 22:15:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-22 22:15:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JYTb8ELS99/ea_profile.json * 2023-11-22 22:15:46 (2293) [INFO] Backed up EA4 profile to /tmp/JYTb8ELS99/ea_profile.json * 2023-11-22 22:15: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-22 22:15:47 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-23 22:14:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-23 22:14:21 (1752) [INFO] Checking if your system is up to date: * 2023-11-23 22:14:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-23 22:14:21 (4229) [INFO] * 2023-11-23 22:14:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-23 22:14:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-23 22:14:21 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-23 22:14:21 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-23 22:14:21 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-23 22:14:21 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-23 22:14:21 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-23 22:14:21 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-23 22:14:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-23 22:14:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-23 22:14:22 (4259) [INFO] * 2023-11-23 22:14:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-23 22:14:22 (4229) [INFO] * 2023-11-23 22:14:52 (4242) [INFO] * 2023-11-23 22:14:52 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-23 22:14:52 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-23 22:14:52 (4259) [INFO] * 2023-11-23 22:14:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-23 22:14:52 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-23 22:15:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-23 22:15:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/61lzS5KvId/ea_profile.json * 2023-11-23 22:15:25 (2293) [INFO] Backed up EA4 profile to /tmp/61lzS5KvId/ea_profile.json * 2023-11-23 22:15: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-11-23 22:15:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-24 22:14:50 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-24 22:14:50 (1752) [INFO] Checking if your system is up to date: * 2023-11-24 22:14:50 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-24 22:14:50 (4229) [INFO] * 2023-11-24 22:14:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-24 22:14:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-24 22:14:50 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-24 22:14:50 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-24 22:14:50 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-24 22:14:50 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-24 22:14:50 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-24 22:14:50 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-24 22:14:51 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-24 22:14:51 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-24 22:14:51 (4259) [INFO] * 2023-11-24 22:14:51 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-24 22:14:51 (4229) [INFO] * 2023-11-24 22:15:24 (4242) [INFO] * 2023-11-24 22:15:24 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-24 22:15:24 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-24 22:15:25 (4259) [INFO] * 2023-11-24 22:15:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-24 22:15:25 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-24 22:15:58 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading * 2023-11-24 22:15:58 (1619) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 12330. Another app is currently holding the yum lock; waiting for it to exit... The other application is: yum Memory : 57 M RSS (379 MB VSZ) Started: Fri Nov 24 22:15:00 2023 - 00:26 ago State : Running, pid: 12330 * 2023-11-24 22:15:58 (155) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2023-11-24 22:16:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-24 22:16:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NRH0DKaHbf/ea_profile.json * 2023-11-24 22:16:02 (2293) [INFO] Backed up EA4 profile to /tmp/NRH0DKaHbf/ea_profile.json * 2023-11-24 22:16: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-11-24 22:16:03 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-25 22:15:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-25 22:15:24 (1752) [INFO] Checking if your system is up to date: * 2023-11-25 22:15:24 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-25 22:15:24 (4229) [INFO] * 2023-11-25 22:15:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-25 22:15:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-25 22:15:25 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-25 22:15:25 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-25 22:15:25 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-25 22:15:25 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-25 22:15:25 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-25 22:15:25 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-25 22:15:25 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-25 22:15:25 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-25 22:15:25 (4259) [INFO] * 2023-11-25 22:15:25 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-25 22:15:25 (4229) [INFO] * 2023-11-25 22:15:58 (4242) [INFO] * 2023-11-25 22:15:58 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-25 22:15:58 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-25 22:15:58 (4259) [INFO] * 2023-11-25 22:15:58 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-25 22:15:58 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-25 22:16:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-25 22:16:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AY4AklCazn/ea_profile.json * 2023-11-25 22:16:30 (2293) [INFO] Backed up EA4 profile to /tmp/AY4AklCazn/ea_profile.json * 2023-11-25 22:16: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-11-25 22:16:31 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-26 22:15:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-26 22:15:19 (1752) [INFO] Checking if your system is up to date: * 2023-11-26 22:15:19 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-26 22:15:19 (4229) [INFO] * 2023-11-26 22:15:20 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-26 22:15:20 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-26 22:15:20 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-26 22:15:20 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-26 22:15:20 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-26 22:15:20 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-26 22:15:20 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-26 22:15:20 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-26 22:15:20 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-26 22:15:20 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-26 22:15:20 (4259) [INFO] * 2023-11-26 22:15:20 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-26 22:15:20 (4229) [INFO] * 2023-11-26 22:15:57 (4242) [INFO] * 2023-11-26 22:15:57 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-26 22:15:57 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-26 22:15:57 (4259) [INFO] * 2023-11-26 22:15:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-26 22:15:57 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-26 22:16:26 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-26 22:16:26 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RFriP9mVxK/ea_profile.json * 2023-11-26 22:16:27 (2293) [INFO] Backed up EA4 profile to /tmp/RFriP9mVxK/ea_profile.json * 2023-11-26 22:16: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-11-26 22:16:29 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-27 22:14:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-27 22:14:22 (1752) [INFO] Checking if your system is up to date: * 2023-11-27 22:14:22 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-27 22:14:22 (4229) [INFO] * 2023-11-27 22:14:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-27 22:14:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-27 22:14:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-27 22:14:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-27 22:14:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-27 22:14:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-27 22:14:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-27 22:14:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-27 22:14:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-27 22:14:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-27 22:14:22 (4259) [INFO] * 2023-11-27 22:14:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-27 22:14:22 (4229) [INFO] * 2023-11-27 22:14:54 (4242) [INFO] * 2023-11-27 22:14:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-27 22:14:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-27 22:14:55 (4259) [INFO] * 2023-11-27 22:14:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-27 22:14:55 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-27 22:15:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-27 22:15:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yIThXHnLZS/ea_profile.json * 2023-11-27 22:15:34 (2293) [INFO] Backed up EA4 profile to /tmp/yIThXHnLZS/ea_profile.json * 2023-11-27 22:15: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-27 22:15:36 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-28 22:14:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-28 22:14:21 (1752) [INFO] Checking if your system is up to date: * 2023-11-28 22:14:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-28 22:14:21 (4229) [INFO] * 2023-11-28 22:14:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-28 22:14:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-28 22:14:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-28 22:14:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-28 22:14:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-28 22:14:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-28 22:14:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-28 22:14:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-28 22:14:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-28 22:14:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-28 22:14:22 (4259) [INFO] * 2023-11-28 22:14:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-28 22:14:22 (4229) [INFO] * 2023-11-28 22:14:54 (4242) [INFO] * 2023-11-28 22:14:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-28 22:14:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-28 22:14:54 (4259) [INFO] * 2023-11-28 22:14:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-28 22:14:54 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-28 22:15:28 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-28 22:15:28 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N2NO6N7oA1/ea_profile.json * 2023-11-28 22:15:30 (2293) [INFO] Backed up EA4 profile to /tmp/N2NO6N7oA1/ea_profile.json * 2023-11-28 22:15: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-11-28 22:15:31 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-29 22:14:18 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-29 22:14:18 (1752) [INFO] Checking if your system is up to date: * 2023-11-29 22:14:18 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-29 22:14:18 (4229) [INFO] * 2023-11-29 22:14:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-29 22:14:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-29 22:14:18 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-29 22:14:18 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-29 22:14:18 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-29 22:14:18 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-29 22:14:18 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-29 22:14:18 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-29 22:14:19 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-29 22:14:19 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-29 22:14:19 (4259) [INFO] * 2023-11-29 22:14:19 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-29 22:14:19 (4229) [INFO] * 2023-11-29 22:14:51 (4242) [INFO] * 2023-11-29 22:14:51 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-29 22:14:51 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-29 22:14:51 (4259) [INFO] * 2023-11-29 22:14:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-29 22:14:51 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-29 22:15:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-29 22:15:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UI1j6WB6nN/ea_profile.json * 2023-11-29 22:15:25 (2293) [INFO] Backed up EA4 profile to /tmp/UI1j6WB6nN/ea_profile.json * 2023-11-29 22:15: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-11-29 22:15:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-11-30 22:14:31 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-11-30 22:14:31 (1752) [INFO] Checking if your system is up to date: * 2023-11-30 22:14:31 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-11-30 22:14:31 (4229) [INFO] * 2023-11-30 22:14:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-11-30 22:14:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-11-30 22:14:32 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-11-30 22:14:32 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-11-30 22:14:32 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-11-30 22:14:32 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-11-30 22:14:32 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-11-30 22:14:32 (4242) [INFO] : wp-toolkit-thirdparties * 2023-11-30 22:14:32 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-11-30 22:14:32 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-11-30 22:14:32 (4259) [INFO] * 2023-11-30 22:14:32 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-11-30 22:14:32 (4229) [INFO] * 2023-11-30 22:15:03 (4242) [INFO] * 2023-11-30 22:15:03 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-11-30 22:15:03 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-11-30 22:15:03 (4259) [INFO] * 2023-11-30 22:15:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-11-30 22:15:03 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-11-30 22:15:32 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-11-30 22:15:32 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qNEb7nlMYp/ea_profile.json * 2023-11-30 22:15:33 (2293) [INFO] Backed up EA4 profile to /tmp/qNEb7nlMYp/ea_profile.json * 2023-11-30 22:15: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-11-30 22:15:34 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-01 22:16:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-01 22:16:21 (1752) [INFO] Checking if your system is up to date: * 2023-12-01 22:16:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-01 22:16:21 (4229) [INFO] * 2023-12-01 22:16:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-01 22:16:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-01 22:16:21 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-01 22:16:21 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-01 22:16:21 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-01 22:16:21 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-01 22:16:21 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-01 22:16:21 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-01 22:16:21 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-01 22:16:21 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-01 22:16:21 (4259) [INFO] * 2023-12-01 22:16:21 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-01 22:16:21 (4229) [INFO] * 2023-12-01 22:16:52 (4242) [INFO] * 2023-12-01 22:16:52 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-01 22:16:52 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-01 22:16:52 (4259) [INFO] * 2023-12-01 22:16:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-01 22:16:52 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-01 22:17:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-01 22:17:21 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yXRq256Wyt/ea_profile.json * 2023-12-01 22:17:22 (2293) [INFO] Backed up EA4 profile to /tmp/yXRq256Wyt/ea_profile.json * 2023-12-01 22:17: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-12-01 22:17:23 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-02 22:15:23 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-02 22:15:23 (1752) [INFO] Checking if your system is up to date: * 2023-12-02 22:15:23 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-02 22:15:23 (4229) [INFO] * 2023-12-02 22:15:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-02 22:15:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-02 22:15:23 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-02 22:15:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-02 22:15:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-02 22:15:23 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-02 22:15:23 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-02 22:15:23 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-02 22:15:23 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-02 22:15:23 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-02 22:15:23 (4259) [INFO] * 2023-12-02 22:15:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-02 22:15:23 (4229) [INFO] * 2023-12-02 22:15:59 (4242) [INFO] * 2023-12-02 22:15:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-02 22:15:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-02 22:15:59 (4259) [INFO] * 2023-12-02 22:15:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-02 22:15:59 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-02 22:16:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-02 22:16:29 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KON9S379gG/ea_profile.json * 2023-12-02 22:16:31 (2293) [INFO] Backed up EA4 profile to /tmp/KON9S379gG/ea_profile.json * 2023-12-02 22:16:33 (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 22:16:33 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-03 22:15:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-03 22:15:21 (1752) [INFO] Checking if your system is up to date: * 2023-12-03 22:15:21 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-03 22:15:21 (4229) [INFO] * 2023-12-03 22:15:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-03 22:15:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-03 22:15:22 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-03 22:15:22 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-03 22:15:22 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-03 22:15:22 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-03 22:15:22 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-03 22:15:22 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-03 22:15:22 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-03 22:15:22 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-03 22:15:22 (4259) [INFO] * 2023-12-03 22:15:22 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-03 22:15:22 (4229) [INFO] * 2023-12-03 22:15:55 (4242) [INFO] * 2023-12-03 22:15:55 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-03 22:15:55 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-03 22:15:55 (4259) [INFO] * 2023-12-03 22:15:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-03 22:15:55 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-03 22:16:24 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-03 22:16:24 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dj3T3BuaIk/ea_profile.json * 2023-12-03 22:16:25 (2293) [INFO] Backed up EA4 profile to /tmp/dj3T3BuaIk/ea_profile.json * 2023-12-03 22:16: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-03 22:16:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-04 22:14:23 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-04 22:14:23 (1752) [INFO] Checking if your system is up to date: * 2023-12-04 22:14:23 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-04 22:14:23 (4229) [INFO] * 2023-12-04 22:14:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-04 22:14:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-04 22:14:23 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-04 22:14:23 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-04 22:14:23 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-04 22:14:23 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-04 22:14:23 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-04 22:14:23 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-04 22:14:23 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-04 22:14:23 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-04 22:14:23 (4259) [INFO] * 2023-12-04 22:14:23 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-04 22:14:23 (4229) [INFO] * 2023-12-04 22:14:54 (4242) [INFO] * 2023-12-04 22:14:54 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-04 22:14:54 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-04 22:14:54 (4259) [INFO] * 2023-12-04 22:14:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-04 22:14:54 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-04 22:15:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-04 22:15:27 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hoWrZ4Hi9n/ea_profile.json * 2023-12-04 22:15:28 (2293) [INFO] Backed up EA4 profile to /tmp/hoWrZ4Hi9n/ea_profile.json * 2023-12-04 22:15: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-12-04 22:15:30 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-05 22:14:40 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-05 22:14:40 (1752) [INFO] Checking if your system is up to date: * 2023-12-05 22:14:40 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-05 22:14:40 (4229) [INFO] * 2023-12-05 22:14:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-05 22:14:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-05 22:14:41 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-05 22:14:41 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-05 22:14:41 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-05 22:14:41 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-05 22:14:41 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-05 22:14:41 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-05 22:14:41 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-05 22:14:41 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-05 22:14:41 (4259) [INFO] * 2023-12-05 22:14:41 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-05 22:14:41 (4229) [INFO] * 2023-12-05 22:15:21 (4242) [INFO] * 2023-12-05 22:15:21 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-05 22:15:21 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-05 22:15:21 (4259) [INFO] * 2023-12-05 22:15:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-05 22:15:21 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-05 22:16:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-05 22:16:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/s4LBw2uASD/ea_profile.json * 2023-12-05 22:16:04 (2293) [INFO] Backed up EA4 profile to /tmp/s4LBw2uASD/ea_profile.json * 2023-12-05 22:16:06 (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 22:16:06 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-06 22:14:18 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-06 22:14:18 (1752) [INFO] Checking if your system is up to date: * 2023-12-06 22:14:18 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-06 22:14:18 (4229) [INFO] * 2023-12-06 22:14:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-06 22:14:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-06 22:14:18 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-06 22:14:18 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-06 22:14:18 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-06 22:14:18 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-06 22:14:18 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-06 22:14:18 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-06 22:14:18 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-06 22:14:18 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-06 22:14:18 (4259) [INFO] * 2023-12-06 22:14:18 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-06 22:14:18 (4229) [INFO] * 2023-12-06 22:14:48 (4242) [INFO] * 2023-12-06 22:14:48 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-06 22:14:48 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-06 22:14:49 (4259) [INFO] * 2023-12-06 22:14:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-06 22:14:49 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-06 22:15:20 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-06 22:15:20 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6im1G3EYWJ/ea_profile.json * 2023-12-06 22:15:21 (2293) [INFO] Backed up EA4 profile to /tmp/6im1G3EYWJ/ea_profile.json * 2023-12-06 22:15: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-12-06 22:15:22 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-07 22:16:33 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-07 22:16:33 (1752) [INFO] Checking if your system is up to date: * 2023-12-07 22:16:33 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-07 22:16:33 (4229) [INFO] * 2023-12-07 22:16:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-07 22:16:34 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-07 22:16:34 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-07 22:16:34 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-07 22:16:34 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-07 22:16:34 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-07 22:16:34 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-07 22:16:34 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-07 22:16:34 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-07 22:16:34 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-07 22:16:34 (4259) [INFO] * 2023-12-07 22:16:34 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-07 22:16:34 (4229) [INFO] * 2023-12-07 22:17:04 (4242) [INFO] * 2023-12-07 22:17:04 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-07 22:17:04 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-07 22:17:05 (4259) [INFO] * 2023-12-07 22:17:05 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-07 22:17:05 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-07 22:17:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-07 22:17:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Scsud0V3kI/ea_profile.json * 2023-12-07 22:17:39 (2293) [INFO] Backed up EA4 profile to /tmp/Scsud0V3kI/ea_profile.json * 2023-12-07 22:17: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-12-07 22:17:40 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-08 22:15:59 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-08 22:15:59 (1752) [INFO] Checking if your system is up to date: * 2023-12-08 22:15:59 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-08 22:15:59 (4229) [INFO] * 2023-12-08 22:16:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-08 22:16:00 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-08 22:16:00 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-08 22:16:00 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-08 22:16:00 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-08 22:16:00 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-08 22:16:00 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-08 22:16:00 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-08 22:16:00 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-08 22:16:00 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-08 22:16:00 (4259) [INFO] * 2023-12-08 22:16:00 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-08 22:16:00 (4229) [INFO] * 2023-12-08 22:16:35 (4242) [INFO] * 2023-12-08 22:16:35 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-08 22:16:35 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-08 22:16:35 (4259) [INFO] * 2023-12-08 22:16:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-08 22:16:35 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-08 22:17:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-08 22:17:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZBSzS8WoOF/ea_profile.json * 2023-12-08 22:17:10 (2293) [INFO] Backed up EA4 profile to /tmp/ZBSzS8WoOF/ea_profile.json * 2023-12-08 22:17: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-12-08 22:17:11 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-09 22:15:25 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-09 22:15:25 (1752) [INFO] Checking if your system is up to date: * 2023-12-09 22:15:25 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-09 22:15:25 (4229) [INFO] * 2023-12-09 22:15:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-09 22:15:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-09 22:15:26 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-09 22:15:26 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-09 22:15:26 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-09 22:15:26 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-09 22:15:26 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-09 22:15:26 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-09 22:15:26 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-09 22:15:26 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-09 22:15:26 (4259) [INFO] * 2023-12-09 22:15:26 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-09 22:15:26 (4229) [INFO] * 2023-12-09 22:15:59 (4242) [INFO] * 2023-12-09 22:15:59 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-09 22:15:59 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-09 22:15:59 (4259) [INFO] * 2023-12-09 22:15:59 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-09 22:15:59 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-09 22:16:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-09 22:16:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Q_jVnxCYrX/ea_profile.json * 2023-12-09 22:16:31 (2293) [INFO] Backed up EA4 profile to /tmp/Q_jVnxCYrX/ea_profile.json * 2023-12-09 22:16: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-12-09 22:16:32 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-10 22:15:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-10 22:15:19 (1752) [INFO] Checking if your system is up to date: * 2023-12-10 22:15:19 (4228) [INFO] Running: /usr/bin/yum clean all * 2023-12-10 22:15:19 (4229) [INFO] * 2023-12-10 22:15:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-10 22:15:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-10 22:15:19 (4242) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-10 22:15:19 (4242) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-10 22:15:19 (4242) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-10 22:15:19 (4242) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-10 22:15:19 (4242) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-10 22:15:19 (4242) [INFO] : wp-toolkit-thirdparties * 2023-12-10 22:15:19 (4242) [INFO] Cleaning up list of fastest mirrors * 2023-12-10 22:15:19 (4242) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-10 22:15:19 (4259) [INFO] * 2023-12-10 22:15:19 (4228) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-10 22:15:19 (4229) [INFO] * 2023-12-10 22:15:53 (4242) [INFO] * 2023-12-10 22:15:53 (4242) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-10 22:15:53 (4242) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-10 22:15:53 (4259) [INFO] * 2023-12-10 22:15:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-10 22:15:53 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-10 22:16:23 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-10 22:16:23 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Cys1FLY6FR/ea_profile.json * 2023-12-10 22:16:24 (2293) [INFO] Backed up EA4 profile to /tmp/Cys1FLY6FR/ea_profile.json * 2023-12-10 22:16:25 (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 22:16:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-11 22:14:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-11 22:14:19 (1753) [INFO] Checking if your system is up to date: * 2023-12-11 22:14:19 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-11 22:14:19 (4230) [INFO] * 2023-12-11 22:14:19 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-11 22:14:19 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-11 22:14:19 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-11 22:14:19 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-11 22:14:19 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-11 22:14:19 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-11 22:14:19 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-11 22:14:19 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-11 22:14:20 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-11 22:14:20 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-11 22:14:20 (4260) [INFO] * 2023-12-11 22:14:20 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-11 22:14:20 (4230) [INFO] * 2023-12-11 22:14:48 (4243) [INFO] * 2023-12-11 22:14:48 (4243) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-11 22:14:48 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-11 22:14:48 (4260) [INFO] * 2023-12-11 22:14:48 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-11 22:14:48 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-11 22:15:23 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-11 22:15:23 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5bYivSWhnr/ea_profile.json * 2023-12-11 22:15:25 (2294) [INFO] Backed up EA4 profile to /tmp/5bYivSWhnr/ea_profile.json * 2023-12-11 22:15: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-12-11 22:15:26 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-12 22:14:35 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-12 22:14:35 (1753) [INFO] Checking if your system is up to date: * 2023-12-12 22:14:35 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-12 22:14:35 (4230) [INFO] * 2023-12-12 22:14:36 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-12 22:14:36 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-12 22:14:36 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-12 22:14:36 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-12 22:14:36 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-12 22:14:36 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-12 22:14:36 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-12 22:14:36 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-12 22:14:36 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-12 22:14:36 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-12 22:14:36 (4260) [INFO] * 2023-12-12 22:14:36 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-12 22:14:36 (4230) [INFO] * 2023-12-12 22:15:11 (4243) [INFO] * 2023-12-12 22:15:11 (4243) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-12 22:15:11 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-12 22:15:11 (4260) [INFO] * 2023-12-12 22:15:11 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-12 22:15:11 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-12 22:15:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-12 22:15:42 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c0PTXoqZgq/ea_profile.json * 2023-12-12 22:15:43 (2294) [INFO] Backed up EA4 profile to /tmp/c0PTXoqZgq/ea_profile.json * 2023-12-12 22:15: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 22:15:48 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-13 22:14:14 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-13 22:14:14 (1753) [INFO] Checking if your system is up to date: * 2023-12-13 22:14:14 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-13 22:14:14 (4230) [INFO] * 2023-12-13 22:14:14 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-13 22:14:15 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-13 22:14:15 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-13 22:14:15 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-13 22:14:15 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-13 22:14:15 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-13 22:14:15 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-13 22:14:15 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-13 22:14:15 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-13 22:14:15 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-13 22:14:15 (4260) [INFO] * 2023-12-13 22:14:15 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-13 22:14:15 (4230) [INFO] * 2023-12-13 22:14:46 (4243) [INFO] * 2023-12-13 22:14:46 (4243) [INFO] kernel.x86_64 3.10.0-1160.102.1.el7 updates * 2023-12-13 22:14:46 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-13 22:14:46 (4260) [INFO] * 2023-12-13 22:14:46 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-13 22:14:46 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-13 22:15:19 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-13 22:15:19 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e23ouR9Dse/ea_profile.json * 2023-12-13 22:15:20 (2294) [INFO] Backed up EA4 profile to /tmp/e23ouR9Dse/ea_profile.json * 2023-12-13 22:15:21 (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 22:15:21 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-14 22:17:55 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-14 22:17:55 (1753) [INFO] Checking if your system is up to date: * 2023-12-14 22:17:55 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-14 22:17:55 (4230) [INFO] * 2023-12-14 22:17:55 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-14 22:17:55 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-14 22:17:55 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-14 22:17:55 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-14 22:17:55 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-14 22:17:55 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-14 22:17:55 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-14 22:17:55 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-14 22:17:56 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-14 22:17:56 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-14 22:17:56 (4260) [INFO] * 2023-12-14 22:17:56 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-14 22:17:56 (4230) [INFO] * 2023-12-14 22:18:26 (4243) [INFO] * 2023-12-14 22:18:26 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-14 22:18:26 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-14 22:18:27 (4260) [INFO] * 2023-12-14 22:18:27 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-14 22:18:27 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-14 22:18:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-14 22:18:58 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dr_T7DG2ON/ea_profile.json * 2023-12-14 22:18:59 (2294) [INFO] Backed up EA4 profile to /tmp/dr_T7DG2ON/ea_profile.json * 2023-12-14 22:19:00 (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 22:19:00 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-15 22:14:26 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-15 22:14:26 (1753) [INFO] Checking if your system is up to date: * 2023-12-15 22:14:26 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-15 22:14:26 (4230) [INFO] * 2023-12-15 22:14:27 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-15 22:14:27 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-15 22:14:27 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-15 22:14:27 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-15 22:14:27 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-15 22:14:27 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-15 22:14:27 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-15 22:14:27 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-15 22:14:27 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-15 22:14:27 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-15 22:14:27 (4260) [INFO] * 2023-12-15 22:14:27 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-15 22:14:27 (4230) [INFO] * 2023-12-15 22:14:58 (4243) [INFO] * 2023-12-15 22:14:58 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-15 22:14:58 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-15 22:14:58 (4260) [INFO] * 2023-12-15 22:14:58 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-15 22:14:58 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-15 22:15:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-15 22:15:29 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HRsW2dJmrK/ea_profile.json * 2023-12-15 22:15:31 (2294) [INFO] Backed up EA4 profile to /tmp/HRsW2dJmrK/ea_profile.json * 2023-12-15 22:15: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-12-15 22:15:36 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-16 22:15:24 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-16 22:15:24 (1753) [INFO] Checking if your system is up to date: * 2023-12-16 22:15:24 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-16 22:15:24 (4230) [INFO] * 2023-12-16 22:15:24 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-16 22:15:24 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-16 22:15:24 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-16 22:15:24 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-16 22:15:24 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-16 22:15:24 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-16 22:15:24 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-16 22:15:24 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-16 22:15:24 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-16 22:15:24 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-16 22:15:24 (4260) [INFO] * 2023-12-16 22:15:24 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-16 22:15:24 (4230) [INFO] * 2023-12-16 22:15:58 (4243) [INFO] * 2023-12-16 22:15:58 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-16 22:15:58 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-16 22:15:58 (4260) [INFO] * 2023-12-16 22:15:58 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-16 22:15:58 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-16 22:16:31 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-16 22:16:31 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ut501QRkOr/ea_profile.json * 2023-12-16 22:16:32 (2294) [INFO] Backed up EA4 profile to /tmp/ut501QRkOr/ea_profile.json * 2023-12-16 22:16: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-12-16 22:16:34 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-17 22:15:21 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-17 22:15:21 (1753) [INFO] Checking if your system is up to date: * 2023-12-17 22:15:21 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-17 22:15:21 (4230) [INFO] * 2023-12-17 22:15:21 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-17 22:15:21 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-17 22:15:21 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-17 22:15:21 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-17 22:15:21 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-17 22:15:21 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-17 22:15:21 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-17 22:15:21 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-17 22:15:21 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-17 22:15:21 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-17 22:15:21 (4260) [INFO] * 2023-12-17 22:15:21 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-17 22:15:21 (4230) [INFO] * 2023-12-17 22:16:01 (4243) [INFO] * 2023-12-17 22:16:01 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-17 22:16:01 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-17 22:16:01 (4260) [INFO] * 2023-12-17 22:16:01 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-17 22:16:01 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-17 22:16:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-17 22:16:33 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6EhzgM_wrQ/ea_profile.json * 2023-12-17 22:16:35 (2294) [INFO] Backed up EA4 profile to /tmp/6EhzgM_wrQ/ea_profile.json * 2023-12-17 22:16: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-12-17 22:16:36 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-18 22:14:22 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-18 22:14:22 (1753) [INFO] Checking if your system is up to date: * 2023-12-18 22:14:22 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-18 22:14:22 (4230) [INFO] * 2023-12-18 22:14:22 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-18 22:14:22 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-18 22:14:22 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-18 22:14:22 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-18 22:14:22 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-18 22:14:22 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-18 22:14:22 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-18 22:14:22 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-18 22:14:22 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-18 22:14:22 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-18 22:14:23 (4260) [INFO] * 2023-12-18 22:14:23 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-18 22:14:23 (4230) [INFO] * 2023-12-18 22:14:53 (4243) [INFO] * 2023-12-18 22:14:53 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-18 22:14:53 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-18 22:14:53 (4260) [INFO] * 2023-12-18 22:14:53 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-18 22:14:53 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-18 22:15:25 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-18 22:15:25 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TmqQIsqSOI/ea_profile.json * 2023-12-18 22:15:26 (2294) [INFO] Backed up EA4 profile to /tmp/TmqQIsqSOI/ea_profile.json * 2023-12-18 22:15: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-18 22:15:27 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-19 22:14:28 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-19 22:14:28 (1753) [INFO] Checking if your system is up to date: * 2023-12-19 22:14:28 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-19 22:14:28 (4230) [INFO] * 2023-12-19 22:14:28 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-19 22:14:29 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-19 22:14:29 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-19 22:14:29 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-19 22:14:29 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-19 22:14:29 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-19 22:14:29 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-19 22:14:29 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-19 22:14:29 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-19 22:14:29 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-19 22:14:29 (4260) [INFO] * 2023-12-19 22:14:29 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-19 22:14:29 (4230) [INFO] * 2023-12-19 22:15:00 (4243) [INFO] * 2023-12-19 22:15:00 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-19 22:15:00 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-19 22:15:01 (4260) [INFO] * 2023-12-19 22:15:01 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-19 22:15:01 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-19 22:15:32 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-19 22:15:32 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F_pNQrBCVJ/ea_profile.json * 2023-12-19 22:15:33 (2294) [INFO] Backed up EA4 profile to /tmp/F_pNQrBCVJ/ea_profile.json * 2023-12-19 22:15: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-12-19 22:15:35 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-20 22:16:19 (155) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-20 22:16:19 (1753) [INFO] Checking if your system is up to date: * 2023-12-20 22:16:19 (4229) [INFO] Running: /usr/bin/yum clean all * 2023-12-20 22:16:19 (4230) [INFO] * 2023-12-20 22:16:19 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-20 22:16:19 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-20 22:16:19 (4243) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-20 22:16:19 (4243) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-20 22:16:19 (4243) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-20 22:16:19 (4243) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-20 22:16:19 (4243) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-20 22:16:19 (4243) [INFO] : wp-toolkit-thirdparties * 2023-12-20 22:16:19 (4243) [INFO] Cleaning up list of fastest mirrors * 2023-12-20 22:16:19 (4243) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-20 22:16:19 (4260) [INFO] * 2023-12-20 22:16:19 (4229) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-20 22:16:19 (4230) [INFO] * 2023-12-20 22:16:50 (4243) [INFO] * 2023-12-20 22:16:50 (4243) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-20 22:16:50 (4243) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-20 22:16:50 (4260) [INFO] * 2023-12-20 22:16:50 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-20 22:16:50 (155) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-20 22:17:21 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-20 22:17:21 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tLmcacxIot/ea_profile.json * 2023-12-20 22:17:23 (2294) [INFO] Backed up EA4 profile to /tmp/tLmcacxIot/ea_profile.json * 2023-12-20 22:17: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-20 22:17:24 (260) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-21 22:14:48 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-21 22:14:49 (1774) [INFO] Checking if your system is up to date: * 2023-12-21 22:14:49 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-21 22:14:49 (4251) [INFO] * 2023-12-21 22:14:49 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-21 22:14:49 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-21 22:14:49 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-21 22:14:49 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-21 22:14:49 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-21 22:14:49 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-21 22:14:49 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-21 22:14:49 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-21 22:14:49 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-21 22:14:49 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-21 22:14:49 (4281) [INFO] * 2023-12-21 22:14:49 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-21 22:14:49 (4251) [INFO] * 2023-12-21 22:15:21 (4264) [INFO] * 2023-12-21 22:15:21 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-21 22:15:21 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-21 22:15:21 (4281) [INFO] * 2023-12-21 22:15:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-21 22:15:21 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-21 22:15:54 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-21 22:15:54 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Cu9YpNuK1J/ea_profile.json * 2023-12-21 22:15:55 (2315) [INFO] Backed up EA4 profile to /tmp/Cu9YpNuK1J/ea_profile.json * 2023-12-21 22:15:56 (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 22:15:56 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-22 22:14:18 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-22 22:14:18 (1774) [INFO] Checking if your system is up to date: * 2023-12-22 22:14:18 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-22 22:14:18 (4251) [INFO] * 2023-12-22 22:14:18 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-22 22:14:19 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-22 22:14:19 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-22 22:14:19 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-22 22:14:19 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-22 22:14:19 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-22 22:14:19 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-22 22:14:19 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-22 22:14:19 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-22 22:14:19 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-22 22:14:19 (4281) [INFO] * 2023-12-22 22:14:19 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-22 22:14:19 (4251) [INFO] * 2023-12-22 22:14:49 (4264) [INFO] * 2023-12-22 22:14:49 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-22 22:14:49 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-22 22:14:49 (4281) [INFO] * 2023-12-22 22:14:49 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-22 22:14:49 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-22 22:15:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-22 22:15:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4spJOjA7x4/ea_profile.json * 2023-12-22 22:15:24 (2315) [INFO] Backed up EA4 profile to /tmp/4spJOjA7x4/ea_profile.json * 2023-12-22 22:15: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 * 2023-12-22 22:15:25 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-23 22:15:33 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-23 22:15:33 (1774) [INFO] Checking if your system is up to date: * 2023-12-23 22:15:33 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-23 22:15:33 (4251) [INFO] * 2023-12-23 22:15:34 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-23 22:15:34 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-23 22:15:34 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-23 22:15:34 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-23 22:15:34 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-23 22:15:34 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-23 22:15:34 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-23 22:15:34 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-23 22:15:34 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-23 22:15:34 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-23 22:15:34 (4281) [INFO] * 2023-12-23 22:15:34 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-23 22:15:34 (4251) [INFO] * 2023-12-23 22:16:08 (4264) [INFO] * 2023-12-23 22:16:08 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-23 22:16:08 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-23 22:16:08 (4281) [INFO] * 2023-12-23 22:16:08 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-23 22:16:08 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-23 22:16:40 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-23 22:16:40 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kbbmCqXy2s/ea_profile.json * 2023-12-23 22:16:41 (2315) [INFO] Backed up EA4 profile to /tmp/kbbmCqXy2s/ea_profile.json * 2023-12-23 22:16: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 * 2023-12-23 22:16:42 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-24 22:15:22 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-24 22:15:22 (1774) [INFO] Checking if your system is up to date: * 2023-12-24 22:15:22 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-24 22:15:22 (4251) [INFO] * 2023-12-24 22:15:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-24 22:15:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-24 22:15:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-24 22:15:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-24 22:15:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-24 22:15:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-24 22:15:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-24 22:15:22 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-24 22:15:22 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-24 22:15:22 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-24 22:15:22 (4281) [INFO] * 2023-12-24 22:15:22 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-24 22:15:22 (4251) [INFO] * 2023-12-24 22:15:56 (4264) [INFO] * 2023-12-24 22:15:56 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-24 22:15:56 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-24 22:15:56 (4281) [INFO] * 2023-12-24 22:15:56 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-24 22:15:56 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-24 22:16:27 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-24 22:16:27 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H0KG0H9V5Q/ea_profile.json * 2023-12-24 22:16:28 (2315) [INFO] Backed up EA4 profile to /tmp/H0KG0H9V5Q/ea_profile.json * 2023-12-24 22:16:29 (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 22:16:29 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-25 22:14:22 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-25 22:14:22 (1774) [INFO] Checking if your system is up to date: * 2023-12-25 22:14:22 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-25 22:14:22 (4251) [INFO] * 2023-12-25 22:14:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-25 22:14:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-25 22:14:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-25 22:14:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-25 22:14:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-25 22:14:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-25 22:14:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-25 22:14:22 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-25 22:14:22 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-25 22:14:22 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-25 22:14:22 (4281) [INFO] * 2023-12-25 22:14:22 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-25 22:14:22 (4251) [INFO] * 2023-12-25 22:14:53 (4264) [INFO] * 2023-12-25 22:14:53 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-25 22:14:53 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-25 22:14:53 (4281) [INFO] * 2023-12-25 22:14:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-25 22:14:53 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-25 22:15:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-25 22:15:28 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gmWuYusnxd/ea_profile.json * 2023-12-25 22:15:29 (2315) [INFO] Backed up EA4 profile to /tmp/gmWuYusnxd/ea_profile.json * 2023-12-25 22:15: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 * 2023-12-25 22:15:30 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-26 22:14:26 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-26 22:14:26 (1774) [INFO] Checking if your system is up to date: * 2023-12-26 22:14:26 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-26 22:14:26 (4251) [INFO] * 2023-12-26 22:14:26 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-26 22:14:26 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-26 22:14:26 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-26 22:14:26 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-26 22:14:26 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-26 22:14:26 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-26 22:14:26 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-26 22:14:26 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-26 22:14:26 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-26 22:14:26 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-26 22:14:26 (4281) [INFO] * 2023-12-26 22:14:26 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-26 22:14:26 (4251) [INFO] * 2023-12-26 22:14:58 (4264) [INFO] * 2023-12-26 22:14:58 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-26 22:14:58 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-26 22:14:58 (4281) [INFO] * 2023-12-26 22:14:58 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-26 22:14:58 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-26 22:15:29 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-26 22:15:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D0erpETLrS/ea_profile.json * 2023-12-26 22:15:30 (2315) [INFO] Backed up EA4 profile to /tmp/D0erpETLrS/ea_profile.json * 2023-12-26 22:15:31 (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 22:15:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-27 22:14:21 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-27 22:14:21 (1774) [INFO] Checking if your system is up to date: * 2023-12-27 22:14:21 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-27 22:14:21 (4251) [INFO] * 2023-12-27 22:14:21 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-27 22:14:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-27 22:14:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-27 22:14:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-27 22:14:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-27 22:14:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-27 22:14:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-27 22:14:22 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-27 22:14:22 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-27 22:14:22 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-27 22:14:22 (4281) [INFO] * 2023-12-27 22:14:22 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-27 22:14:22 (4251) [INFO] * 2023-12-27 22:14:52 (4264) [INFO] * 2023-12-27 22:14:52 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-27 22:14:52 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-27 22:14:53 (4281) [INFO] * 2023-12-27 22:14:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-27 22:14:53 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-27 22:15:26 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-27 22:15:26 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g5EQ5t2rDO/ea_profile.json * 2023-12-27 22:15:28 (2315) [INFO] Backed up EA4 profile to /tmp/g5EQ5t2rDO/ea_profile.json * 2023-12-27 22:15:29 (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 22:15:29 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-28 22:14:19 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-28 22:14:19 (1774) [INFO] Checking if your system is up to date: * 2023-12-28 22:14:19 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-28 22:14:19 (4251) [INFO] * 2023-12-28 22:14:19 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-28 22:14:19 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-28 22:14:19 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-28 22:14:19 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-28 22:14:19 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-28 22:14:19 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-28 22:14:19 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-28 22:14:19 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-28 22:14:20 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-28 22:14:20 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-28 22:14:20 (4281) [INFO] * 2023-12-28 22:14:20 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-28 22:14:20 (4251) [INFO] * 2023-12-28 22:14:50 (4264) [INFO] * 2023-12-28 22:14:50 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-28 22:14:50 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-28 22:14:50 (4281) [INFO] * 2023-12-28 22:14:50 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-28 22:14:50 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-28 22:15:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-28 22:15:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/otUTX00Kce/ea_profile.json * 2023-12-28 22:15:24 (2315) [INFO] Backed up EA4 profile to /tmp/otUTX00Kce/ea_profile.json * 2023-12-28 22:15: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 * 2023-12-28 22:15:25 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-29 22:14:23 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-29 22:14:23 (1774) [INFO] Checking if your system is up to date: * 2023-12-29 22:14:23 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-29 22:14:23 (4251) [INFO] * 2023-12-29 22:14:23 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-29 22:14:23 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-29 22:14:23 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-29 22:14:23 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-29 22:14:23 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-29 22:14:23 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-29 22:14:23 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-29 22:14:23 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-29 22:14:23 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-29 22:14:23 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-29 22:14:23 (4281) [INFO] * 2023-12-29 22:14:23 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-29 22:14:23 (4251) [INFO] * 2023-12-29 22:14:55 (4264) [INFO] * 2023-12-29 22:14:55 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-29 22:14:55 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-29 22:14:55 (4281) [INFO] * 2023-12-29 22:14:55 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-29 22:14:55 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-29 22:15:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-29 22:15:28 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XADpZgfRud/ea_profile.json * 2023-12-29 22:15:30 (2315) [INFO] Backed up EA4 profile to /tmp/XADpZgfRud/ea_profile.json * 2023-12-29 22:15:31 (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 22:15:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-30 22:15:24 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-30 22:15:24 (1774) [INFO] Checking if your system is up to date: * 2023-12-30 22:15:24 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-30 22:15:24 (4251) [INFO] * 2023-12-30 22:15:24 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-30 22:15:24 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-30 22:15:24 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-30 22:15:24 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-30 22:15:24 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-30 22:15:24 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-30 22:15:24 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-30 22:15:24 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-30 22:15:24 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-30 22:15:25 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-30 22:15:25 (4281) [INFO] * 2023-12-30 22:15:25 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-30 22:15:25 (4251) [INFO] * 2023-12-30 22:15:58 (4264) [INFO] * 2023-12-30 22:15:58 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-30 22:15:58 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-30 22:15:58 (4281) [INFO] * 2023-12-30 22:15:58 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-30 22:15:58 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-30 22:16:30 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-30 22:16:30 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oDmxNpohDz/ea_profile.json * 2023-12-30 22:16:31 (2315) [INFO] Backed up EA4 profile to /tmp/oDmxNpohDz/ea_profile.json * 2023-12-30 22:16: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 * 2023-12-30 22:16:32 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2023-12-31 22:15:14 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2023-12-31 22:15:14 (1774) [INFO] Checking if your system is up to date: * 2023-12-31 22:15:14 (4250) [INFO] Running: /usr/bin/yum clean all * 2023-12-31 22:15:14 (4251) [INFO] * 2023-12-31 22:15:14 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2023-12-31 22:15:14 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2023-12-31 22:15:14 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2023-12-31 22:15:14 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2023-12-31 22:15:14 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2023-12-31 22:15:14 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2023-12-31 22:15:14 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2023-12-31 22:15:14 (4264) [INFO] : wp-toolkit-thirdparties * 2023-12-31 22:15:14 (4264) [INFO] Cleaning up list of fastest mirrors * 2023-12-31 22:15:14 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2023-12-31 22:15:14 (4281) [INFO] * 2023-12-31 22:15:14 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2023-12-31 22:15:14 (4251) [INFO] * 2023-12-31 22:15:48 (4264) [INFO] * 2023-12-31 22:15:48 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2023-12-31 22:15:48 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2023-12-31 22:15:49 (4281) [INFO] * 2023-12-31 22:15:49 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2023-12-31 22:15:49 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2023-12-31 22:16:22 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2023-12-31 22:16:22 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/if0TgkVpTN/ea_profile.json * 2023-12-31 22:16:23 (2315) [INFO] Backed up EA4 profile to /tmp/if0TgkVpTN/ea_profile.json * 2023-12-31 22:16: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 * 2023-12-31 22:16:24 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-01 22:14:21 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-01 22:14:21 (1774) [INFO] Checking if your system is up to date: * 2024-01-01 22:14:21 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-01 22:14:21 (4251) [INFO] * 2024-01-01 22:14:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-01 22:14:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-01 22:14:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-01 22:14:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-01 22:14:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-01 22:14:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-01 22:14:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-01 22:14:22 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-01 22:14:22 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-01 22:14:22 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-01 22:14:22 (4281) [INFO] * 2024-01-01 22:14:22 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-01 22:14:22 (4251) [INFO] * 2024-01-01 22:14:55 (4264) [INFO] * 2024-01-01 22:14:55 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-01 22:14:55 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-01 22:14:56 (4281) [INFO] * 2024-01-01 22:14:56 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-01 22:14:56 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-01 22:15:29 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-01 22:15:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I7ZElQPBj0/ea_profile.json * 2024-01-01 22:15:30 (2315) [INFO] Backed up EA4 profile to /tmp/I7ZElQPBj0/ea_profile.json * 2024-01-01 22:15:31 (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 22:15:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-02 22:14:20 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-02 22:14:20 (1774) [INFO] Checking if your system is up to date: * 2024-01-02 22:14:20 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-02 22:14:20 (4251) [INFO] * 2024-01-02 22:14:20 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-02 22:14:20 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-02 22:14:20 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-02 22:14:20 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-02 22:14:20 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-02 22:14:20 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-02 22:14:20 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-02 22:14:20 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-02 22:14:21 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-02 22:14:21 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-02 22:14:21 (4281) [INFO] * 2024-01-02 22:14:21 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-02 22:14:21 (4251) [INFO] * 2024-01-02 22:14:50 (4264) [INFO] * 2024-01-02 22:14:50 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-02 22:14:50 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-02 22:14:50 (4281) [INFO] * 2024-01-02 22:14:50 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-02 22:14:50 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-02 22:15:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-02 22:15:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/1UAVEktuiw/ea_profile.json * 2024-01-02 22:15:24 (2315) [INFO] Backed up EA4 profile to /tmp/1UAVEktuiw/ea_profile.json * 2024-01-02 22:15: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-01-02 22:15:25 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-03 22:14:19 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-03 22:14:19 (1774) [INFO] Checking if your system is up to date: * 2024-01-03 22:14:19 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-03 22:14:19 (4251) [INFO] * 2024-01-03 22:14:19 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-03 22:14:19 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-03 22:14:19 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-03 22:14:19 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-03 22:14:19 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-03 22:14:19 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-03 22:14:19 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-03 22:14:19 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-03 22:14:20 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-03 22:14:20 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-03 22:14:20 (4281) [INFO] * 2024-01-03 22:14:20 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-03 22:14:20 (4251) [INFO] * 2024-01-03 22:14:49 (4264) [INFO] * 2024-01-03 22:14:49 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-03 22:14:49 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-03 22:14:49 (4281) [INFO] * 2024-01-03 22:14:49 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-03 22:14:49 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-03 22:15:21 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-03 22:15:22 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hcwCQ3mcgC/ea_profile.json * 2024-01-03 22:15:24 (2315) [INFO] Backed up EA4 profile to /tmp/hcwCQ3mcgC/ea_profile.json * 2024-01-03 22:15: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-01-03 22:15:25 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-04 22:14:47 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-04 22:14:47 (1774) [INFO] Checking if your system is up to date: * 2024-01-04 22:14:47 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-04 22:14:47 (4251) [INFO] * 2024-01-04 22:14:47 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-04 22:14:48 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-04 22:14:48 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-04 22:14:48 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-04 22:14:48 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-04 22:14:48 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-04 22:14:48 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-04 22:14:48 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-04 22:14:48 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-04 22:14:48 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-04 22:14:48 (4281) [INFO] * 2024-01-04 22:14:48 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-04 22:14:48 (4251) [INFO] * 2024-01-04 22:15:21 (4264) [INFO] * 2024-01-04 22:15:21 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-04 22:15:21 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-04 22:15:21 (4281) [INFO] * 2024-01-04 22:15:21 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-04 22:15:21 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-04 22:15:53 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-04 22:15:53 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qUthf3aKBC/ea_profile.json * 2024-01-04 22:15:55 (2315) [INFO] Backed up EA4 profile to /tmp/qUthf3aKBC/ea_profile.json * 2024-01-04 22:15:56 (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 22:15:56 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-05 22:14:25 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-05 22:14:25 (1774) [INFO] Checking if your system is up to date: * 2024-01-05 22:14:25 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-05 22:14:25 (4251) [INFO] * 2024-01-05 22:14:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-05 22:14:26 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-05 22:14:26 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-05 22:14:26 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-05 22:14:26 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-05 22:14:26 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-05 22:14:26 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-05 22:14:26 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-05 22:14:26 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-05 22:14:26 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-05 22:14:26 (4281) [INFO] * 2024-01-05 22:14:26 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-05 22:14:26 (4251) [INFO] * 2024-01-05 22:14:55 (4264) [INFO] * 2024-01-05 22:14:55 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-05 22:14:55 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-05 22:14:55 (4281) [INFO] * 2024-01-05 22:14:55 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-05 22:14:55 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-05 22:15:31 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-05 22:15:31 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xByvOf7cTF/ea_profile.json * 2024-01-05 22:15:33 (2315) [INFO] Backed up EA4 profile to /tmp/xByvOf7cTF/ea_profile.json * 2024-01-05 22:15:34 (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 22:15:34 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-06 22:15:25 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-06 22:15:25 (1774) [INFO] Checking if your system is up to date: * 2024-01-06 22:15:25 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-06 22:15:25 (4251) [INFO] * 2024-01-06 22:15:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-06 22:15:26 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-06 22:15:26 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-06 22:15:26 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-06 22:15:26 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-06 22:15:26 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-06 22:15:26 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-06 22:15:26 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-06 22:15:26 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-06 22:15:26 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-06 22:15:26 (4281) [INFO] * 2024-01-06 22:15:26 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-06 22:15:26 (4251) [INFO] * 2024-01-06 22:16:00 (4264) [INFO] * 2024-01-06 22:16:00 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-06 22:16:00 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-06 22:16:00 (4281) [INFO] * 2024-01-06 22:16:00 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-06 22:16:00 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-06 22:16:30 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-06 22:16:30 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HgG72xGuvv/ea_profile.json * 2024-01-06 22:16:31 (2315) [INFO] Backed up EA4 profile to /tmp/HgG72xGuvv/ea_profile.json * 2024-01-06 22:16:33 (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 22:16:33 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-07 22:15:15 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-07 22:15:15 (1774) [INFO] Checking if your system is up to date: * 2024-01-07 22:15:15 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-07 22:15:15 (4251) [INFO] * 2024-01-07 22:15:15 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-07 22:15:15 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-07 22:15:15 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-07 22:15:15 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-07 22:15:15 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-07 22:15:15 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-07 22:15:15 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-07 22:15:15 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-07 22:15:15 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-07 22:15:15 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-07 22:15:15 (4281) [INFO] * 2024-01-07 22:15:15 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-07 22:15:15 (4251) [INFO] * 2024-01-07 22:15:53 (4264) [INFO] * 2024-01-07 22:15:53 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-07 22:15:53 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-07 22:15:53 (4281) [INFO] * 2024-01-07 22:15:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-07 22:15:53 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-07 22:16:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-07 22:16:23 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h3Nd_Hsrb8/ea_profile.json * 2024-01-07 22:16:24 (2315) [INFO] Backed up EA4 profile to /tmp/h3Nd_Hsrb8/ea_profile.json * 2024-01-07 22:16: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-01-07 22:16:25 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-08 22:14:27 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-08 22:14:27 (1774) [INFO] Checking if your system is up to date: * 2024-01-08 22:14:27 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-08 22:14:27 (4251) [INFO] * 2024-01-08 22:14:27 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-08 22:14:28 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-08 22:14:28 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-08 22:14:28 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-08 22:14:28 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-08 22:14:28 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-08 22:14:28 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-08 22:14:28 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-08 22:14:28 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-08 22:14:28 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-08 22:14:28 (4281) [INFO] * 2024-01-08 22:14:28 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-08 22:14:28 (4251) [INFO] * 2024-01-08 22:14:57 (4264) [INFO] * 2024-01-08 22:14:57 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-08 22:14:57 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-08 22:14:57 (4281) [INFO] * 2024-01-08 22:14:57 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-08 22:14:57 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-08 22:15:29 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-08 22:15:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hE138nKmnn/ea_profile.json * 2024-01-08 22:15:30 (2315) [INFO] Backed up EA4 profile to /tmp/hE138nKmnn/ea_profile.json * 2024-01-08 22:15:31 (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 22:15:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-09 22:14:22 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-09 22:14:22 (1774) [INFO] Checking if your system is up to date: * 2024-01-09 22:14:22 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-09 22:14:22 (4251) [INFO] * 2024-01-09 22:14:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-09 22:14:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-09 22:14:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-09 22:14:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-09 22:14:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-09 22:14:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-09 22:14:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-09 22:14:22 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-09 22:14:23 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-09 22:14:23 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-09 22:14:23 (4281) [INFO] * 2024-01-09 22:14:23 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-09 22:14:23 (4251) [INFO] * 2024-01-09 22:14:55 (4264) [INFO] * 2024-01-09 22:14:55 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-09 22:14:55 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-09 22:14:55 (4281) [INFO] * 2024-01-09 22:14:55 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-09 22:14:55 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-09 22:15:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-09 22:15:28 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/edazFxD_ic/ea_profile.json * 2024-01-09 22:15:29 (2315) [INFO] Backed up EA4 profile to /tmp/edazFxD_ic/ea_profile.json * 2024-01-09 22:15: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-09 22:15:30 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-10 22:15:12 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-10 22:15:12 (1774) [INFO] Checking if your system is up to date: * 2024-01-10 22:15:12 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-10 22:15:12 (4251) [INFO] * 2024-01-10 22:15:13 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-10 22:15:13 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-10 22:15:13 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-10 22:15:13 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-10 22:15:13 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-10 22:15:13 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-10 22:15:13 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-10 22:15:13 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-10 22:15:13 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-10 22:15:13 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-10 22:15:13 (4281) [INFO] * 2024-01-10 22:15:13 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-10 22:15:13 (4251) [INFO] * 2024-01-10 22:15:51 (4264) [INFO] * 2024-01-10 22:15:51 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-10 22:15:51 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-10 22:15:51 (4281) [INFO] * 2024-01-10 22:15:51 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-10 22:15:51 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-10 22:16:24 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-10 22:16:25 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MbBofwfUgv/ea_profile.json * 2024-01-10 22:16:28 (2315) [INFO] Backed up EA4 profile to /tmp/MbBofwfUgv/ea_profile.json * 2024-01-10 22:16:29 (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 22:16:29 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-11 22:16:42 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-11 22:16:42 (1774) [INFO] Checking if your system is up to date: * 2024-01-11 22:16:42 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-11 22:16:42 (4251) [INFO] * 2024-01-11 22:16:42 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-11 22:16:43 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-11 22:16:43 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-11 22:16:43 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-11 22:16:43 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-11 22:16:43 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-11 22:16:43 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-11 22:16:43 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-11 22:16:43 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-11 22:16:43 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-11 22:16:43 (4281) [INFO] * 2024-01-11 22:16:43 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-11 22:16:43 (4251) [INFO] * 2024-01-11 22:17:25 (4264) [INFO] * 2024-01-11 22:17:25 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-11 22:17:25 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-11 22:17:25 (4281) [INFO] * 2024-01-11 22:17:25 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-11 22:17:25 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-11 22:18:17 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-11 22:18:17 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zM7LN2rZQq/ea_profile.json * 2024-01-11 22:18:18 (2315) [INFO] Backed up EA4 profile to /tmp/zM7LN2rZQq/ea_profile.json * 2024-01-11 22:18:19 (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 22:18:19 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-12 22:14:20 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-12 22:14:20 (1774) [INFO] Checking if your system is up to date: * 2024-01-12 22:14:20 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-12 22:14:20 (4251) [INFO] * 2024-01-12 22:14:20 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-12 22:14:20 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-12 22:14:20 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-12 22:14:20 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-12 22:14:20 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-12 22:14:20 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-12 22:14:20 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-12 22:14:20 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-12 22:14:20 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-12 22:14:20 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-12 22:14:20 (4281) [INFO] * 2024-01-12 22:14:20 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-12 22:14:20 (4251) [INFO] * 2024-01-12 22:14:49 (4264) [INFO] * 2024-01-12 22:14:49 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-12 22:14:49 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-12 22:14:50 (4281) [INFO] * 2024-01-12 22:14:50 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-12 22:14:50 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-12 22:15:25 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-12 22:15:25 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2FtG2_Vubz/ea_profile.json * 2024-01-12 22:15:26 (2315) [INFO] Backed up EA4 profile to /tmp/2FtG2_Vubz/ea_profile.json * 2024-01-12 22:15:27 (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 22:15:28 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-13 22:15:22 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-13 22:15:22 (1774) [INFO] Checking if your system is up to date: * 2024-01-13 22:15:22 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-13 22:15:22 (4251) [INFO] * 2024-01-13 22:15:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-13 22:15:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-13 22:15:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-13 22:15:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-13 22:15:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-13 22:15:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-13 22:15:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-13 22:15:22 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-13 22:15:23 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-13 22:15:23 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-13 22:15:23 (4281) [INFO] * 2024-01-13 22:15:23 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-13 22:15:23 (4251) [INFO] * 2024-01-13 22:15:53 (4264) [INFO] * 2024-01-13 22:15:53 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-13 22:15:53 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-13 22:15:54 (4281) [INFO] * 2024-01-13 22:15:54 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-13 22:15:54 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-13 22:16:31 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-13 22:16:31 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rB5ZQqD7Wo/ea_profile.json * 2024-01-13 22:16:33 (2315) [INFO] Backed up EA4 profile to /tmp/rB5ZQqD7Wo/ea_profile.json * 2024-01-13 22:16:34 (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 22:16:34 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-14 22:15:22 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-14 22:15:22 (1774) [INFO] Checking if your system is up to date: * 2024-01-14 22:15:22 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-14 22:15:22 (4251) [INFO] * 2024-01-14 22:15:22 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-14 22:15:22 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-14 22:15:22 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-14 22:15:22 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-14 22:15:22 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-14 22:15:22 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-14 22:15:22 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-14 22:15:22 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-14 22:15:23 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-14 22:15:23 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-14 22:15:23 (4281) [INFO] * 2024-01-14 22:15:23 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-14 22:15:23 (4251) [INFO] * 2024-01-14 22:15:52 (4264) [INFO] * 2024-01-14 22:15:52 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-14 22:15:52 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-14 22:15:52 (4281) [INFO] * 2024-01-14 22:15:52 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-14 22:15:52 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-14 22:16:20 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-14 22:16:20 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o6rcI7s9Rm/ea_profile.json * 2024-01-14 22:16:22 (2315) [INFO] Backed up EA4 profile to /tmp/o6rcI7s9Rm/ea_profile.json * 2024-01-14 22:16:23 (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 22:16:23 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-15 22:14:20 (161) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-01-15 22:14:21 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-15 22:14:21 (1774) [INFO] Checking if your system is up to date: * 2024-01-15 22:14:21 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-15 22:14:21 (4251) [INFO] * 2024-01-15 22:14:21 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-15 22:14:21 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-15 22:14:21 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-15 22:14:21 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-15 22:14:21 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-15 22:14:21 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-15 22:14:21 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-15 22:14:21 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-15 22:14:21 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-15 22:14:21 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-15 22:14:21 (4281) [INFO] * 2024-01-15 22:14:21 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-15 22:14:21 (4251) [INFO] * 2024-01-15 22:14:53 (4264) [INFO] * 2024-01-15 22:14:53 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-15 22:14:53 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-15 22:14:54 (4281) [INFO] * 2024-01-15 22:14:54 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-15 22:14:54 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-15 22:15:28 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-15 22:15:28 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4T9H2F2csY/ea_profile.json * 2024-01-15 22:15:30 (2315) [INFO] Backed up EA4 profile to /tmp/4T9H2F2csY/ea_profile.json * 2024-01-15 22:15:31 (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 22:15:31 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-01-16 22:14:19 (161) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-01-16 22:14:20 (161) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-01-16 22:14:20 (1774) [INFO] Checking if your system is up to date: * 2024-01-16 22:14:20 (4250) [INFO] Running: /usr/bin/yum clean all * 2024-01-16 22:14:20 (4251) [INFO] * 2024-01-16 22:14:20 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-01-16 22:14:20 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-01-16 22:14:20 (4264) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-01-16 22:14:20 (4264) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-01-16 22:14:20 (4264) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-01-16 22:14:20 (4264) [INFO] : mysql-connectors-community mysql-tools-community * 2024-01-16 22:14:20 (4264) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-01-16 22:14:20 (4264) [INFO] : wp-toolkit-thirdparties * 2024-01-16 22:14:20 (4264) [INFO] Cleaning up list of fastest mirrors * 2024-01-16 22:14:20 (4264) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-01-16 22:14:20 (4281) [INFO] * 2024-01-16 22:14:20 (4250) [INFO] Running: /usr/bin/yum check-update -q * 2024-01-16 22:14:20 (4251) [INFO] * 2024-01-16 22:14:51 (4264) [INFO] * 2024-01-16 22:14:51 (4264) [INFO] kernel.x86_64 3.10.0-1160.105.1.el7 updates * 2024-01-16 22:14:51 (4264) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-01-16 22:14:51 (4281) [INFO] * 2024-01-16 22:14:51 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-01-16 22:14:51 (161) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-01-16 22:15:23 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-01-16 22:15:24 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/koF_h4HgtR/ea_profile.json * 2024-01-16 22:15:25 (2315) [INFO] Backed up EA4 profile to /tmp/koF_h4HgtR/ea_profile.json * 2024-01-16 22:15:26 (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 22:15:26 (268) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-17 22:19:20 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-02-17 22:19:21 (163) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-17 22:19:21 (1845) [INFO] Checking if your system is up to date: * 2024-02-17 22:19:21 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-17 22:19:21 (4463) [INFO] * 2024-02-17 22:19:21 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-17 22:19:22 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 5344. * 2024-02-17 22:19:22 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:22 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:22 (4476) [INFO] Memory : 122 M RSS (426 MB VSZ) * 2024-02-17 22:19:22 (4476) [INFO] Started: Sat Feb 17 22:19:14 2024 - 00:08 ago * 2024-02-17 22:19:22 (4476) [INFO] State : Running, pid: 5344 * 2024-02-17 22:19:24 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:24 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:24 (4476) [INFO] Memory : 139 M RSS (443 MB VSZ) * 2024-02-17 22:19:24 (4476) [INFO] Started: Sat Feb 17 22:19:14 2024 - 00:10 ago * 2024-02-17 22:19:24 (4476) [INFO] State : Running, pid: 5344 * 2024-02-17 22:19:26 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:26 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:26 (4476) [INFO] Memory : 116 M RSS (409 MB VSZ) * 2024-02-17 22:19:26 (4476) [INFO] Started: Sat Feb 17 22:19:14 2024 - 00:12 ago * 2024-02-17 22:19:26 (4476) [INFO] State : Uninterruptible, pid: 5344 * 2024-02-17 22:19:28 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:28 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:28 (4476) [INFO] Memory : 116 M RSS (409 MB VSZ) * 2024-02-17 22:19:28 (4476) [INFO] Started: Sat Feb 17 22:19:14 2024 - 00:14 ago * 2024-02-17 22:19:28 (4476) [INFO] State : Uninterruptible, pid: 5344 * 2024-02-17 22:19:30 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:30 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:30 (4476) [INFO] Memory : 116 M RSS (409 MB VSZ) * 2024-02-17 22:19:30 (4476) [INFO] Started: Sat Feb 17 22:19:14 2024 - 00:16 ago * 2024-02-17 22:19:30 (4476) [INFO] State : Uninterruptible, pid: 5344 * 2024-02-17 22:19:32 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-17 22:19:32 (4476) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-17 22:19:32 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-17 22:19:32 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-17 22:19:32 (4476) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-17 22:19:32 (4476) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-17 22:19:32 (4476) [INFO] : wp-toolkit-thirdparties * 2024-02-17 22:19:32 (4476) [INFO] Cleaning up list of fastest mirrors * 2024-02-17 22:19:32 (4476) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-17 22:19:32 (4493) [INFO] * 2024-02-17 22:19:32 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-17 22:19:32 (4463) [INFO] * 2024-02-17 22:19:33 (4476) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 5473. * 2024-02-17 22:19:33 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:33 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:33 (4476) [INFO] Memory : 26 M RSS (318 MB VSZ) * 2024-02-17 22:19:33 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:01 ago * 2024-02-17 22:19:33 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:19:35 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:35 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:35 (4476) [INFO] Memory : 30 M RSS (1.6 GB VSZ) * 2024-02-17 22:19:35 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:03 ago * 2024-02-17 22:19:35 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:19:37 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:37 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:37 (4476) [INFO] Memory : 30 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:37 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:05 ago * 2024-02-17 22:19:37 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:19:39 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:39 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:39 (4476) [INFO] Memory : 31 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:39 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:07 ago * 2024-02-17 22:19:39 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:19:41 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:41 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:41 (4476) [INFO] Memory : 31 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:41 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:09 ago * 2024-02-17 22:19:41 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:19:43 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:43 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:43 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:43 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:11 ago * 2024-02-17 22:19:43 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:45 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:45 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:45 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:45 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:13 ago * 2024-02-17 22:19:45 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:47 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:47 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:47 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:47 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:15 ago * 2024-02-17 22:19:47 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:49 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:49 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:49 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:49 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:17 ago * 2024-02-17 22:19:49 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:51 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:51 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:51 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:51 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:19 ago * 2024-02-17 22:19:51 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:53 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:53 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:53 (4476) [INFO] Memory : 36 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:53 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:21 ago * 2024-02-17 22:19:53 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:55 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:55 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:55 (4476) [INFO] Memory : 58 M RSS (1.2 GB VSZ) * 2024-02-17 22:19:55 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:23 ago * 2024-02-17 22:19:55 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:57 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:57 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:57 (4476) [INFO] Memory : 123 M RSS (1.3 GB VSZ) * 2024-02-17 22:19:57 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:25 ago * 2024-02-17 22:19:57 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:19:59 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:19:59 (4476) [INFO] The other application is: yum * 2024-02-17 22:19:59 (4476) [INFO] Memory : 123 M RSS (1.3 GB VSZ) * 2024-02-17 22:19:59 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:27 ago * 2024-02-17 22:19:59 (4476) [INFO] State : Running, pid: 5473 * 2024-02-17 22:20:01 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:20:01 (4476) [INFO] The other application is: yum * 2024-02-17 22:20:01 (4476) [INFO] Memory : 128 M RSS (1.3 GB VSZ) * 2024-02-17 22:20:01 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:29 ago * 2024-02-17 22:20:01 (4476) [INFO] State : Uninterruptible, pid: 5473 * 2024-02-17 22:20:03 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:20:03 (4476) [INFO] The other application is: yum * 2024-02-17 22:20:03 (4476) [INFO] Memory : 128 M RSS (1.3 GB VSZ) * 2024-02-17 22:20:03 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:31 ago * 2024-02-17 22:20:03 (4476) [INFO] State : Uninterruptible, pid: 5473 * 2024-02-17 22:20:05 (4476) [INFO] Another app is currently holding the yum lock; waiting for it to exit... * 2024-02-17 22:20:05 (4476) [INFO] The other application is: yum * 2024-02-17 22:20:05 (4476) [INFO] Memory : 128 M RSS (1.3 GB VSZ) * 2024-02-17 22:20:05 (4476) [INFO] Started: Sat Feb 17 22:19:32 2024 - 00:33 ago * 2024-02-17 22:20:05 (4476) [INFO] State : Sleeping, pid: 5473 * 2024-02-17 22:20:19 (4476) [INFO] * 2024-02-17 22:20:19 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-17 22:20:19 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-17 22:20:19 (4493) [INFO] * 2024-02-17 22:20:19 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-17 22:20:19 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-17 22:20:49 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-17 22:20:49 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vpUEjOBZiD/ea_profile.json * 2024-02-17 22:20:51 (2437) [INFO] Backed up EA4 profile to /tmp/vpUEjOBZiD/ea_profile.json * 2024-02-17 22:20:51 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-17 22:20: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-17 22:20:52 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-18 22:15:18 (163) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-18 22:15:18 (1845) [INFO] Checking if your system is up to date: * 2024-02-18 22:15:18 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-18 22:15:18 (4463) [INFO] * 2024-02-18 22:15:18 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-18 22:15:19 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-18 22:15:19 (4476) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-18 22:15:19 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-18 22:15:19 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-18 22:15:19 (4476) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-18 22:15:19 (4476) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-18 22:15:19 (4476) [INFO] : wp-toolkit-thirdparties * 2024-02-18 22:15:19 (4476) [INFO] Cleaning up list of fastest mirrors * 2024-02-18 22:15:19 (4476) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-18 22:15:19 (4493) [INFO] * 2024-02-18 22:15:19 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-18 22:15:19 (4463) [INFO] * 2024-02-18 22:15:51 (4476) [INFO] * 2024-02-18 22:15:51 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-18 22:15:51 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-18 22:15:52 (4493) [INFO] * 2024-02-18 22:15:52 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-18 22:15:52 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-18 22:16:31 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-18 22:16:31 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gBJDZoR2oD/ea_profile.json * 2024-02-18 22:16:32 (2437) [INFO] Backed up EA4 profile to /tmp/gBJDZoR2oD/ea_profile.json * 2024-02-18 22:16:32 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-18 22:16:33 (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 22:16:33 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-19 22:15:11 (163) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-19 22:15:11 (1845) [INFO] Checking if your system is up to date: * 2024-02-19 22:15:11 (4462) [INFO] Running: /usr/bin/yum clean all * 2024-02-19 22:15:11 (4463) [INFO] * 2024-02-19 22:15:11 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-19 22:15:11 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-19 22:15:11 (4476) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-19 22:15:11 (4476) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-19 22:15:11 (4476) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-19 22:15:11 (4476) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-19 22:15:11 (4476) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-19 22:15:11 (4476) [INFO] : wp-toolkit-thirdparties * 2024-02-19 22:15:12 (4476) [INFO] Cleaning up list of fastest mirrors * 2024-02-19 22:15:12 (4476) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-19 22:15:12 (4493) [INFO] * 2024-02-19 22:15:12 (4462) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-19 22:15:12 (4463) [INFO] * 2024-02-19 22:15:45 (4476) [INFO] * 2024-02-19 22:15:45 (4476) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-19 22:15:45 (4476) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-19 22:15:45 (4493) [INFO] * 2024-02-19 22:15:45 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-19 22:15:45 (163) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-19 22:16:31 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-19 22:16:31 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XDSd3oYu8i/ea_profile.json * 2024-02-19 22:16:32 (2437) [INFO] Backed up EA4 profile to /tmp/XDSd3oYu8i/ea_profile.json * 2024-02-19 22:16:32 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-19 22:16:33 (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 22:16:33 (271) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-20 22:14:56 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-20 22:14:56 (1782) [INFO] Checking if your system is up to date: * 2024-02-20 22:14:56 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-20 22:14:56 (4911) [INFO] * 2024-02-20 22:14:57 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-20 22:14:57 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-20 22:14:57 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-20 22:14:57 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-20 22:14:57 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-20 22:14:57 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-20 22:14:57 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-20 22:14:57 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-20 22:14:57 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-20 22:14:57 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-20 22:14:57 (4941) [INFO] * 2024-02-20 22:14:57 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-20 22:14:57 (4911) [INFO] * 2024-02-20 22:15:33 (4924) [INFO] * 2024-02-20 22:15:33 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-20 22:15:33 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-20 22:15:33 (4941) [INFO] * 2024-02-20 22:15:33 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-20 22:15:33 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-20 22:16:30 (1641) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-02-20 22:16:30 (1642) [ERROR] http://184.94.196.92/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno 12] Timeout on http://184.94.196.92/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Trying other mirror. http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/a168648430654a927dcc94a55c38cf2253df920819831ba8a746fe09d0907684-other.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. * 2024-02-20 22:16:30 (170) [WARN] *** Elevation Blocker detected: *** yum is not stable * 2024-02-20 22:16:31 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-20 22:16:31 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/r_IUYZEPwp/ea_profile.json * 2024-02-20 22:16:34 (2386) [INFO] Backed up EA4 profile to /tmp/r_IUYZEPwp/ea_profile.json * 2024-02-20 22:16:34 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-20 22:16:35 (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-20 22:16:35 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-21 22:14:31 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-21 22:14:32 (1782) [INFO] Checking if your system is up to date: * 2024-02-21 22:14:32 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-21 22:14:32 (4911) [INFO] * 2024-02-21 22:14:32 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-21 22:14:32 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-21 22:14:32 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-21 22:14:32 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-21 22:14:32 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-21 22:14:32 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-21 22:14:32 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-21 22:14:32 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-21 22:14:32 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-21 22:14:32 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-21 22:14:32 (4941) [INFO] * 2024-02-21 22:14:32 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-21 22:14:32 (4911) [INFO] * 2024-02-21 22:15:04 (4924) [INFO] * 2024-02-21 22:15:04 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-21 22:15:04 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-21 22:15:05 (4941) [INFO] * 2024-02-21 22:15:05 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-21 22:15:05 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-21 22:16:36 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-21 22:16:36 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5ZeU07r4v5/ea_profile.json * 2024-02-21 22:16:37 (2386) [INFO] Backed up EA4 profile to /tmp/5ZeU07r4v5/ea_profile.json * 2024-02-21 22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-21 22:16: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 22:16:38 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-22 22:14:46 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-22 22:14:46 (1782) [INFO] Checking if your system is up to date: * 2024-02-22 22:14:46 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-22 22:14:46 (4911) [INFO] * 2024-02-22 22:14:46 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-22 22:14:47 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-22 22:14:47 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-22 22:14:47 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-22 22:14:47 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-22 22:14:47 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-22 22:14:47 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-22 22:14:47 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-22 22:14:47 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-22 22:14:47 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-22 22:14:47 (4941) [INFO] * 2024-02-22 22:14:47 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-22 22:14:47 (4911) [INFO] * 2024-02-22 22:15:18 (4924) [INFO] * 2024-02-22 22:15:18 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-22 22:15:18 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-22 22:15:18 (4941) [INFO] * 2024-02-22 22:15:18 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-22 22:15:18 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-22 22:16:32 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-22 22:16:32 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X51M32b83u/ea_profile.json * 2024-02-22 22:16:33 (2386) [INFO] Backed up EA4 profile to /tmp/X51M32b83u/ea_profile.json * 2024-02-22 22:16:34 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-22 22:16:34 (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 22:16:34 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-23 22:14:47 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-23 22:14:48 (1782) [INFO] Checking if your system is up to date: * 2024-02-23 22:14:48 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-23 22:14:48 (4911) [INFO] * 2024-02-23 22:14:48 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-23 22:14:48 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-23 22:14:48 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-23 22:14:48 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-23 22:14:48 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-23 22:14:48 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-23 22:14:48 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-23 22:14:48 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-23 22:14:48 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-23 22:14:48 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-23 22:14:48 (4941) [INFO] * 2024-02-23 22:14:48 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-23 22:14:48 (4911) [INFO] * 2024-02-23 22:15:22 (4924) [INFO] * 2024-02-23 22:15:22 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-23 22:15:22 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-23 22:15:22 (4941) [INFO] * 2024-02-23 22:15:22 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-23 22:15:22 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-23 22:15:52 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-23 22:15:52 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e0eIeDmQxK/ea_profile.json * 2024-02-23 22:15:53 (2386) [INFO] Backed up EA4 profile to /tmp/e0eIeDmQxK/ea_profile.json * 2024-02-23 22:15:54 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-23 22:15:54 (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 22:15:55 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-24 22:15:27 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-24 22:15:28 (1782) [INFO] Checking if your system is up to date: * 2024-02-24 22:15:28 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-24 22:15:28 (4911) [INFO] * 2024-02-24 22:15:28 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-24 22:15:28 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-24 22:15:28 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-24 22:15:28 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-24 22:15:28 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-24 22:15:28 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-24 22:15:28 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-24 22:15:28 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-24 22:15:28 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-24 22:15:28 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-24 22:15:28 (4941) [INFO] * 2024-02-24 22:15:28 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-24 22:15:28 (4911) [INFO] * 2024-02-24 22:15:57 (4924) [INFO] * 2024-02-24 22:15:57 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-24 22:15:57 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-24 22:15:58 (4941) [INFO] * 2024-02-24 22:15:58 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-24 22:15:58 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-24 22:16:25 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-24 22:16:25 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_0qMAoHhc9/ea_profile.json * 2024-02-24 22:16:26 (2386) [INFO] Backed up EA4 profile to /tmp/_0qMAoHhc9/ea_profile.json * 2024-02-24 22:16: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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-24 22:16:27 (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 22:16:27 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-25 22:15:19 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-25 22:15:19 (1782) [INFO] Checking if your system is up to date: * 2024-02-25 22:15:19 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-25 22:15:19 (4911) [INFO] * 2024-02-25 22:15:19 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-25 22:15:19 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-25 22:15:19 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-25 22:15:19 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-25 22:15:19 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-25 22:15:19 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-25 22:15:19 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-25 22:15:19 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-25 22:15:19 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-25 22:15:19 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-25 22:15:19 (4941) [INFO] * 2024-02-25 22:15:19 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-25 22:15:19 (4911) [INFO] * 2024-02-25 22:15:51 (4924) [INFO] * 2024-02-25 22:15:51 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-25 22:15:51 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-25 22:15:51 (4941) [INFO] * 2024-02-25 22:15:51 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-25 22:15:51 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-25 22:16:22 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-25 22:16:22 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FeP6kqTsa3/ea_profile.json * 2024-02-25 22:16:23 (2386) [INFO] Backed up EA4 profile to /tmp/FeP6kqTsa3/ea_profile.json * 2024-02-25 22:16:23 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-25 22:16:24 (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 22:16:24 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-26 22:14:22 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-26 22:14:23 (1782) [INFO] Checking if your system is up to date: * 2024-02-26 22:14:23 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-26 22:14:23 (4911) [INFO] * 2024-02-26 22:14:23 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-26 22:14:23 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-26 22:14:23 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-26 22:14:23 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-26 22:14:23 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-26 22:14:23 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-26 22:14:23 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-26 22:14:23 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-26 22:14:23 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-26 22:14:23 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-26 22:14:23 (4941) [INFO] * 2024-02-26 22:14:23 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-26 22:14:23 (4911) [INFO] * 2024-02-26 22:14:51 (4924) [INFO] * 2024-02-26 22:14:51 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-26 22:14:51 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-26 22:14:51 (4941) [INFO] * 2024-02-26 22:14:51 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-26 22:14:51 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-26 22:15:21 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-26 22:15:21 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zx3JSg9rxW/ea_profile.json * 2024-02-26 22:15:22 (2386) [INFO] Backed up EA4 profile to /tmp/zx3JSg9rxW/ea_profile.json * 2024-02-26 22:15:22 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-26 22:15:23 (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 22:15:23 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-27 22:14:22 (170) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-27 22:14:22 (1782) [INFO] Checking if your system is up to date: * 2024-02-27 22:14:22 (4910) [INFO] Running: /usr/bin/yum clean all * 2024-02-27 22:14:22 (4911) [INFO] * 2024-02-27 22:14:23 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-27 22:14:23 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-27 22:14:23 (4924) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-27 22:14:23 (4924) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-27 22:14:23 (4924) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-27 22:14:23 (4924) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-27 22:14:23 (4924) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-27 22:14:23 (4924) [INFO] : wp-toolkit-thirdparties * 2024-02-27 22:14:23 (4924) [INFO] Cleaning up list of fastest mirrors * 2024-02-27 22:14:23 (4924) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-27 22:14:23 (4941) [INFO] * 2024-02-27 22:14:23 (4910) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-27 22:14:23 (4911) [INFO] * 2024-02-27 22:14:52 (4924) [INFO] * 2024-02-27 22:14:52 (4924) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-27 22:14:52 (4924) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-27 22:14:52 (4941) [INFO] * 2024-02-27 22:14:52 (1789) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-27 22:14:52 (170) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-27 22:15:23 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-27 22:15:23 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XsEL3DddWl/ea_profile.json * 2024-02-27 22:15:24 (2386) [INFO] Backed up EA4 profile to /tmp/XsEL3DddWl/ea_profile.json * 2024-02-27 22:15:25 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-27 22:15:27 (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 22:15:28 (278) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-28 22:14:24 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-28 22:14:25 (1828) [INFO] Checking if your system is up to date: * 2024-02-28 22:14:25 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-02-28 22:14:25 (5105) [INFO] * 2024-02-28 22:14:25 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-28 22:14:25 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-28 22:14:25 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-28 22:14:25 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-28 22:14:25 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-28 22:14:25 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-28 22:14:25 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-28 22:14:25 (5118) [INFO] : wp-toolkit-thirdparties * 2024-02-28 22:14:25 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-02-28 22:14:25 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-28 22:14:25 (5135) [INFO] * 2024-02-28 22:14:25 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-28 22:14:25 (5105) [INFO] * 2024-02-28 22:14:56 (5118) [INFO] * 2024-02-28 22:14:56 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-28 22:14:56 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-28 22:14:56 (5135) [INFO] * 2024-02-28 22:14:56 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-28 22:14:56 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-28 22:15:29 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-28 22:15:29 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JEoBOFh0tB/ea_profile.json * 2024-02-28 22:15:31 (2488) [INFO] Backed up EA4 profile to /tmp/JEoBOFh0tB/ea_profile.json * 2024-02-28 22:15:31 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-28 22:15:32 (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 22:15:32 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-02-29 22:15:02 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-02-29 22:15:03 (1828) [INFO] Checking if your system is up to date: * 2024-02-29 22:15:03 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-02-29 22:15:03 (5105) [INFO] * 2024-02-29 22:15:04 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-02-29 22:15:05 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-02-29 22:15:05 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-02-29 22:15:05 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-02-29 22:15:05 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-02-29 22:15:05 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-02-29 22:15:05 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-02-29 22:15:05 (5118) [INFO] : wp-toolkit-thirdparties * 2024-02-29 22:15:05 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-02-29 22:15:05 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-02-29 22:15:05 (5135) [INFO] * 2024-02-29 22:15:05 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-02-29 22:15:05 (5105) [INFO] * 2024-02-29 22:15:40 (5118) [INFO] * 2024-02-29 22:15:40 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-02-29 22:15:40 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-02-29 22:15:40 (5135) [INFO] * 2024-02-29 22:15:40 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-02-29 22:15:40 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-02-29 22:16:11 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-02-29 22:16:11 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CmoFtdyDYQ/ea_profile.json * 2024-02-29 22:16:12 (2488) [INFO] Backed up EA4 profile to /tmp/CmoFtdyDYQ/ea_profile.json * 2024-02-29 22:16:13 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-02-29 22:16:13 (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 22:16:14 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-01 22:14:31 (173) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-01 22:14:32 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-01 22:14:32 (1828) [INFO] Checking if your system is up to date: * 2024-03-01 22:14:32 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-01 22:14:32 (5105) [INFO] * 2024-03-01 22:14:32 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-01 22:14:32 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-01 22:14:32 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-01 22:14:32 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-01 22:14:32 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-01 22:14:32 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-01 22:14:32 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-01 22:14:32 (5118) [INFO] : wp-toolkit-thirdparties * 2024-03-01 22:14:33 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-03-01 22:14:33 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-01 22:14:33 (5135) [INFO] * 2024-03-01 22:14:33 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-01 22:14:33 (5105) [INFO] * 2024-03-01 22:15:04 (5118) [INFO] * 2024-03-01 22:15:04 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-01 22:15:04 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-01 22:15:04 (5135) [INFO] * 2024-03-01 22:15:04 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-01 22:15:04 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-01 22:15:32 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-01 22:15:32 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/86V6_nTv_k/ea_profile.json * 2024-03-01 22:15:34 (2488) [INFO] Backed up EA4 profile to /tmp/86V6_nTv_k/ea_profile.json * 2024-03-01 22:15:34 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-01 22:15:36 (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 22:15:36 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-02 22:15:22 (173) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-02 22:15:23 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-02 22:15:24 (1828) [INFO] Checking if your system is up to date: * 2024-03-02 22:15:24 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-02 22:15:24 (5105) [INFO] * 2024-03-02 22:15:24 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-02 22:15:24 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-02 22:15:24 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-02 22:15:24 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-02 22:15:24 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-02 22:15:24 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-02 22:15:24 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-02 22:15:24 (5118) [INFO] : wp-toolkit-thirdparties * 2024-03-02 22:15:25 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-03-02 22:15:25 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-02 22:15:25 (5135) [INFO] * 2024-03-02 22:15:25 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-02 22:15:25 (5105) [INFO] * 2024-03-02 22:15:55 (5118) [INFO] * 2024-03-02 22:15:55 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-02 22:15:55 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-02 22:15:55 (5135) [INFO] * 2024-03-02 22:15:55 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-02 22:15:55 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-02 22:16:25 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-02 22:16:25 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y7QpTjZ7EG/ea_profile.json * 2024-03-02 22:16:27 (2488) [INFO] Backed up EA4 profile to /tmp/Y7QpTjZ7EG/ea_profile.json * 2024-03-02 22:16:27 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-02 22:16:28 (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-02 22:16:28 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-03 22:15:24 (173) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-03 22:15:25 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-03 22:15:26 (1828) [INFO] Checking if your system is up to date: * 2024-03-03 22:15:26 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-03 22:15:26 (5105) [INFO] * 2024-03-03 22:15:26 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-03 22:15:26 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-03 22:15:26 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-03 22:15:26 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-03 22:15:26 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-03 22:15:26 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-03 22:15:26 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-03 22:15:26 (5118) [INFO] : wp-toolkit-thirdparties * 2024-03-03 22:15:26 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-03-03 22:15:26 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-03 22:15:26 (5135) [INFO] * 2024-03-03 22:15:26 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-03 22:15:26 (5105) [INFO] * 2024-03-03 22:16:03 (5118) [INFO] * 2024-03-03 22:16:03 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-03 22:16:03 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-03 22:16:04 (5135) [INFO] * 2024-03-03 22:16:04 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-03 22:16:04 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-03 22:16:35 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-03 22:16:35 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cDY9bezZa9/ea_profile.json * 2024-03-03 22:16:37 (2488) [INFO] Backed up EA4 profile to /tmp/cDY9bezZa9/ea_profile.json * 2024-03-03 22:16:37 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-03 22:16:38 (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-03 22:16:38 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-04 22:14:24 (173) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-04 22:14:24 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-04 22:14:25 (1828) [INFO] Checking if your system is up to date: * 2024-03-04 22:14:25 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-04 22:14:25 (5105) [INFO] * 2024-03-04 22:14:25 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-04 22:14:25 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-04 22:14:25 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-04 22:14:25 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-04 22:14:25 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-04 22:14:25 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-04 22:14:25 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-04 22:14:25 (5118) [INFO] : wp-toolkit-thirdparties * 2024-03-04 22:14:25 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-03-04 22:14:25 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-04 22:14:25 (5135) [INFO] * 2024-03-04 22:14:25 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-04 22:14:25 (5105) [INFO] * 2024-03-04 22:14:55 (5118) [INFO] * 2024-03-04 22:14:55 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-04 22:14:55 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-04 22:14:55 (5135) [INFO] * 2024-03-04 22:14:55 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-04 22:14:55 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-04 22:15:29 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-04 22:15:29 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v9SMOp8_4P/ea_profile.json * 2024-03-04 22:15:30 (2488) [INFO] Backed up EA4 profile to /tmp/v9SMOp8_4P/ea_profile.json * 2024-03-04 22:15:31 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-04 22:15:31 (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-04 22:15:32 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-05 22:14:19 (173) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-05 22:14:20 (173) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-05 22:14:20 (1828) [INFO] Checking if your system is up to date: * 2024-03-05 22:14:20 (5104) [INFO] Running: /usr/bin/yum clean all * 2024-03-05 22:14:20 (5105) [INFO] * 2024-03-05 22:14:21 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-05 22:14:21 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-05 22:14:21 (5118) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-05 22:14:21 (5118) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-05 22:14:21 (5118) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-05 22:14:21 (5118) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-05 22:14:21 (5118) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-05 22:14:21 (5118) [INFO] : wp-toolkit-thirdparties * 2024-03-05 22:14:21 (5118) [INFO] Cleaning up list of fastest mirrors * 2024-03-05 22:14:21 (5118) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-05 22:14:21 (5135) [INFO] * 2024-03-05 22:14:21 (5104) [INFO] Running: /usr/bin/yum check-update -q * 2024-03-05 22:14:21 (5105) [INFO] * 2024-03-05 22:14:49 (5118) [INFO] * 2024-03-05 22:14:49 (5118) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-05 22:14:49 (5118) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-05 22:14:49 (5135) [INFO] * 2024-03-05 22:14:49 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-05 22:14:49 (173) [WARN] *** Elevation Blocker detected: *** System is not up to date * 2024-03-05 22:15:21 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-05 22:15:21 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6TrgcERivz/ea_profile.json * 2024-03-05 22:15:22 (2488) [INFO] Backed up EA4 profile to /tmp/6TrgcERivz/ea_profile.json * 2024-03-05 22:15:23 (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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-05 22:15:23 (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-05 22:15:24 (283) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-06 22:14:38 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-06 22:14:39 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-06 22:14:39 (1896) [INFO] Checking if your system is up to date: * 2024-03-06 22:14:39 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-06 22:14:39 (5196) [INFO] * 2024-03-06 22:14:40 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-06 22:14:40 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-06 22:14:40 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-06 22:14:40 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-06 22:14:40 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-06 22:14:40 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-06 22:14:40 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-06 22:14:40 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-06 22:14:40 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-06 22:14:40 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-06 22:14:40 (5226) [INFO] * 2024-03-06 22:14:40 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-06 22:14:40 (5196) [INFO] * 2024-03-06 22:15:17 (5209) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 12] Timeout on https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') * 2024-03-06 22:15:17 (5209) [INFO] Trying other mirror. * 2024-03-06 22:15:36 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-06 22:15:36 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-06 22:15:36 (5226) [INFO] * 2024-03-06 22:15:36 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-06 22:16:03 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-06 22:16:03 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ToNg5fsAGS/ea_profile.json * 2024-03-06 22:16:04 (2579) [INFO] Backed up EA4 profile to /tmp/ToNg5fsAGS/ea_profile.json * 2024-03-06 22:16:04 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-06 22:16:05 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-06 22:16:05 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-07 22:14:33 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-07 22:14:34 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-07 22:14:35 (1896) [INFO] Checking if your system is up to date: * 2024-03-07 22:14:35 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-07 22:14:35 (5196) [INFO] * 2024-03-07 22:14:35 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-07 22:14:35 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-07 22:14:35 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-07 22:14:35 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-07 22:14:35 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-07 22:14:35 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-07 22:14:35 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-07 22:14:35 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-07 22:14:35 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-07 22:14:35 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-07 22:14:35 (5226) [INFO] * 2024-03-07 22:14:35 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-07 22:14:35 (5196) [INFO] * 2024-03-07 22:15:06 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-07 22:15:06 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-07 22:15:06 (5226) [INFO] * 2024-03-07 22:15:06 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-07 22:15:36 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-07 22:15:36 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5Gdm5UzWd7/ea_profile.json * 2024-03-07 22:15:37 (2579) [INFO] Backed up EA4 profile to /tmp/5Gdm5UzWd7/ea_profile.json * 2024-03-07 22:15:37 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-07 22:15:38 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-07 22:15:38 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-08 22:14:28 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-08 22:14:29 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-08 22:14:30 (1896) [INFO] Checking if your system is up to date: * 2024-03-08 22:14:30 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-08 22:14:30 (5196) [INFO] * 2024-03-08 22:14:30 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-08 22:14:30 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-08 22:14:30 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-08 22:14:30 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-08 22:14:30 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-08 22:14:30 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-08 22:14:30 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-08 22:14:30 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-08 22:14:30 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-08 22:14:30 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-08 22:14:30 (5226) [INFO] * 2024-03-08 22:14:30 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-08 22:14:30 (5196) [INFO] * 2024-03-08 22:15:03 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-08 22:15:03 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-08 22:15:03 (5226) [INFO] * 2024-03-08 22:15:03 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-08 22:15:35 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-08 22:15:35 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pyKNIn1K2m/ea_profile.json * 2024-03-08 22:15:36 (2579) [INFO] Backed up EA4 profile to /tmp/pyKNIn1K2m/ea_profile.json * 2024-03-08 22:15:37 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-08 22:15:37 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-08 22:15:37 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-09 22:15:23 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-09 22:15:24 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-09 22:15:24 (1896) [INFO] Checking if your system is up to date: * 2024-03-09 22:15:24 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-09 22:15:24 (5196) [INFO] * 2024-03-09 22:15:24 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-09 22:15:24 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-09 22:15:24 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-09 22:15:24 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-09 22:15:24 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-09 22:15:24 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-09 22:15:24 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-09 22:15:24 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-09 22:15:24 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-09 22:15:25 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-09 22:15:25 (5226) [INFO] * 2024-03-09 22:15:25 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-09 22:15:25 (5196) [INFO] * 2024-03-09 22:15:54 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-09 22:15:54 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-09 22:15:54 (5226) [INFO] * 2024-03-09 22:15:54 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-09 22:16:26 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-09 22:16:26 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AHWjqKO4gL/ea_profile.json * 2024-03-09 22:16:27 (2579) [INFO] Backed up EA4 profile to /tmp/AHWjqKO4gL/ea_profile.json * 2024-03-09 22:16:27 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-09 22:16:30 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-09 22:16:30 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-10 22:15:26 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-10 22:15:27 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-10 22:15:27 (1896) [INFO] Checking if your system is up to date: * 2024-03-10 22:15:27 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-10 22:15:27 (5196) [INFO] * 2024-03-10 22:15:27 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-10 22:15:28 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-10 22:15:28 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-10 22:15:28 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-10 22:15:28 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-10 22:15:28 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-10 22:15:28 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-10 22:15:28 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-10 22:15:28 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-10 22:15:28 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-10 22:15:28 (5226) [INFO] * 2024-03-10 22:15:28 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-10 22:15:28 (5196) [INFO] * 2024-03-10 22:16:00 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-10 22:16:00 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-10 22:16:00 (5226) [INFO] * 2024-03-10 22:16:00 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-10 22:16:36 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-10 22:16:36 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/S_QPOXrn7t/ea_profile.json * 2024-03-10 22:16:37 (2579) [INFO] Backed up EA4 profile to /tmp/S_QPOXrn7t/ea_profile.json * 2024-03-10 22:16:37 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-10 22:16:38 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-10 22:16:38 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-11 22:14:15 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-11 22:14:16 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-11 22:14:16 (1896) [INFO] Checking if your system is up to date: * 2024-03-11 22:14:16 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-11 22:14:16 (5196) [INFO] * 2024-03-11 22:14:17 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-11 22:14:17 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-11 22:14:17 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-11 22:14:17 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-11 22:14:17 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-11 22:14:17 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-11 22:14:17 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-11 22:14:17 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-11 22:14:17 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-11 22:14:17 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-11 22:14:17 (5226) [INFO] * 2024-03-11 22:14:17 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-11 22:14:17 (5196) [INFO] * 2024-03-11 22:14:45 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-11 22:14:45 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-11 22:14:45 (5226) [INFO] * 2024-03-11 22:14:45 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-11 22:15:21 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-11 22:15:22 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X1Rsxn7b_s/ea_profile.json * 2024-03-11 22:15:23 (2579) [INFO] Backed up EA4 profile to /tmp/X1Rsxn7b_s/ea_profile.json * 2024-03-11 22:15:23 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-11 22:15:24 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-11 22:15:24 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-12 22:15:08 (190) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-12 22:15:09 (190) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-12 22:15:10 (1896) [INFO] Checking if your system is up to date: * 2024-03-12 22:15:10 (5195) [INFO] Running: /usr/bin/yum clean all * 2024-03-12 22:15:10 (5196) [INFO] * 2024-03-12 22:15:10 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-03-12 22:15:10 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-03-12 22:15:10 (5209) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-03-12 22:15:10 (5209) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-03-12 22:15:10 (5209) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-03-12 22:15:10 (5209) [INFO] : mysql-connectors-community mysql-tools-community * 2024-03-12 22:15:10 (5209) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-03-12 22:15:10 (5209) [INFO] : wp-toolkit-thirdparties * 2024-03-12 22:15:10 (5209) [INFO] Cleaning up list of fastest mirrors * 2024-03-12 22:15:10 (5209) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-03-12 22:15:11 (5226) [INFO] * 2024-03-12 22:15:11 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3 * 2024-03-12 22:15:11 (5196) [INFO] * 2024-03-12 22:15:42 (5209) [INFO] kernel.x86_64 3.10.0-1160.108.1.el7 updates * 2024-03-12 22:15:42 (5209) [INFO] kmod-libs.x86_64 20-28.el7 base * 2024-03-12 22:15:42 (5226) [INFO] * 2024-03-12 22:15:42 (1904) [WARN] Your system is not up to date please run: /usr/bin/yum update * 2024-03-12 22:16:15 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-12 22:16:15 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QnFa3znLMN/ea_profile.json * 2024-03-12 22:16:16 (2579) [INFO] Backed up EA4 profile to /tmp/QnFa3znLMN/ea_profile.json * 2024-03-12 22:16:16 (190) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-12 22:16:17 (190) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-12 22:16:17 (300) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-13 22:14:32 (191) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-13 22:14:32 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-13 22:15:08 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-13 22:15:08 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L2z2ok7fqj/ea_profile.json * 2024-03-13 22:15:09 (2541) [INFO] Backed up EA4 profile to /tmp/L2z2ok7fqj/ea_profile.json * 2024-03-13 22:15:10 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-13 22:15:10 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-13 22:15:10 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-14 22:14:23 (191) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-14 22:14:24 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-14 22:14:56 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-14 22:14:56 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_XVPaHElif/ea_profile.json * 2024-03-14 22:14:57 (2541) [INFO] Backed up EA4 profile to /tmp/_XVPaHElif/ea_profile.json * 2024-03-14 22:14:58 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-14 22:14:58 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-14 22:14:58 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-15 22:14:22 (191) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-03-15 22:14:22 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-15 22:14:52 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-15 22:14:53 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b1rXeOUyLr/ea_profile.json * 2024-03-15 22:14:54 (2541) [INFO] Backed up EA4 profile to /tmp/b1rXeOUyLr/ea_profile.json * 2024-03-15 22:14:54 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-15 22:14:55 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-15 22:14:55 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-16 22:15:15 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-16 22:15:44 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-16 22:15:45 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JkeAI_cvL_/ea_profile.json * 2024-03-16 22:15:46 (2541) [INFO] Backed up EA4 profile to /tmp/JkeAI_cvL_/ea_profile.json * 2024-03-16 22:15:46 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-16 22:15:47 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-16 22:15:47 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-17 22:15:15 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-17 22:15:44 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-17 22:15:44 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/s1YvC7WVS6/ea_profile.json * 2024-03-17 22:15:45 (2541) [INFO] Backed up EA4 profile to /tmp/s1YvC7WVS6/ea_profile.json * 2024-03-17 22:15:45 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-17 22:15:46 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-17 22:15:46 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-18 22:16:15 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-18 22:17:36 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-03-18 22:17:36 (1717) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable" Trying other mirror. https://download.imunify360.com/el/7/slot-3/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer" Trying other mirror. * 2024-03-18 22:17:37 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-18 22:17:37 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uXPPGdk0cU/ea_profile.json * 2024-03-18 22:17:38 (2541) [INFO] Backed up EA4 profile to /tmp/uXPPGdk0cU/ea_profile.json * 2024-03-18 22:17:38 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-18 22:17:39 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-18 22:17:39 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-19 22:14:21 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-19 22:14:49 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-19 22:14:49 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mGo88DcI61/ea_profile.json * 2024-03-19 22:14:51 (2541) [INFO] Backed up EA4 profile to /tmp/mGo88DcI61/ea_profile.json * 2024-03-19 22:14:51 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-19 22:14:52 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-19 22:14:52 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-20 22:15:53 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-20 22:16:21 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-20 22:16:21 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B0w4c_UfMN/ea_profile.json * 2024-03-20 22:16:22 (2541) [INFO] Backed up EA4 profile to /tmp/B0w4c_UfMN/ea_profile.json * 2024-03-20 22:16:23 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-20 22:16:23 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-20 22:16:23 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-21 22:14:21 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-21 22:14:53 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-21 22:14:53 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tAFWj4NW11/ea_profile.json * 2024-03-21 22:14:54 (2541) [INFO] Backed up EA4 profile to /tmp/tAFWj4NW11/ea_profile.json * 2024-03-21 22:14:54 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-21 22:14:55 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-21 22:14:55 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-22 22:14:52 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-22 22:15:24 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-22 22:15:24 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TiiBGnr4G7/ea_profile.json * 2024-03-22 22:15:25 (2541) [INFO] Backed up EA4 profile to /tmp/TiiBGnr4G7/ea_profile.json * 2024-03-22 22:15:25 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-22 22:15:26 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-22 22:15:26 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-23 22:15:14 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-23 22:15:41 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-23 22:15:41 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wuUUwVXLGI/ea_profile.json * 2024-03-23 22:15:43 (2541) [INFO] Backed up EA4 profile to /tmp/wuUUwVXLGI/ea_profile.json * 2024-03-23 22:15:43 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-23 22:15:44 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-23 22:15:44 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-24 22:15:05 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-24 22:15:35 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-24 22:15:35 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lqv83PoEm7/ea_profile.json * 2024-03-24 22:15:36 (2541) [INFO] Backed up EA4 profile to /tmp/lqv83PoEm7/ea_profile.json * 2024-03-24 22:15:36 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-24 22:15:37 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-24 22:15:37 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-25 22:14:27 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-25 22:14:56 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-25 22:14:56 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JGoskW_lHv/ea_profile.json * 2024-03-25 22:14:57 (2541) [INFO] Backed up EA4 profile to /tmp/JGoskW_lHv/ea_profile.json * 2024-03-25 22:14:58 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-25 22:15:01 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-25 22:15:01 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-26 22:14:38 (191) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-26 22:15:10 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-26 22:15:10 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aZQq4yp0DD/ea_profile.json * 2024-03-26 22:15:11 (2541) [INFO] Backed up EA4 profile to /tmp/aZQq4yp0DD/ea_profile.json * 2024-03-26 22:15:11 (191) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-26 22:15:12 (191) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-26 22:15:12 (301) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-27 22:14:20 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-27 22:14:49 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-27 22:14:49 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8GAN5uWmOa/ea_profile.json * 2024-03-27 22:14:51 (2641) [INFO] Backed up EA4 profile to /tmp/8GAN5uWmOa/ea_profile.json * 2024-03-27 22:14:51 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-27 22:14:52 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-27 22:14:54 (2290) [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-03-27 22:14:54 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-28 22:14:35 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-28 22:15:05 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-28 22:15:05 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IIb8T_3ta5/ea_profile.json * 2024-03-28 22:15:06 (2641) [INFO] Backed up EA4 profile to /tmp/IIb8T_3ta5/ea_profile.json * 2024-03-28 22:15:07 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-28 22:15:07 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-28 22:15:08 (2290) [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-03-28 22:15:08 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-29 22:14:16 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-29 22:14:44 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-29 22:14:44 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lyJoBSh0R0/ea_profile.json * 2024-03-29 22:14:46 (2641) [INFO] Backed up EA4 profile to /tmp/lyJoBSh0R0/ea_profile.json * 2024-03-29 22:14:46 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-29 22:14:47 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-29 22:14:51 (2290) [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-03-29 22:14:51 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-30 22:15:45 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-30 22:16:19 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-30 22:16:19 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iPlCrO3CB9/ea_profile.json * 2024-03-30 22:16:21 (2641) [INFO] Backed up EA4 profile to /tmp/iPlCrO3CB9/ea_profile.json * 2024-03-30 22:16:22 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-30 22:16:25 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-30 22:16:26 (2290) [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-03-30 22:16:26 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-03-31 22:15:14 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-03-31 22:15:44 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-03-31 22:15:44 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fVGBvCvX7f/ea_profile.json * 2024-03-31 22:15:45 (2641) [INFO] Backed up EA4 profile to /tmp/fVGBvCvX7f/ea_profile.json * 2024-03-31 22:15:45 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-03-31 22:15:46 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-31 22:15:51 (2290) [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-03-31 22:15:51 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-01 22:14:18 (194) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-04-01 22:14:19 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-01 22:14:52 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-01 22:14:52 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kvgixGhDcK/ea_profile.json * 2024-04-01 22:14:53 (2641) [INFO] Backed up EA4 profile to /tmp/kvgixGhDcK/ea_profile.json * 2024-04-01 22:14:53 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-01 22:14:56 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-01 22:14:57 (2290) [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-04-01 22:14:57 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-02 22:14:19 (194) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-04-02 22:14:20 (194) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-02 22:14:50 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-02 22:14:50 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Pr1wIbIyqR/ea_profile.json * 2024-04-02 22:14:51 (2641) [INFO] Backed up EA4 profile to /tmp/Pr1wIbIyqR/ea_profile.json * 2024-04-02 22:14:51 (194) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-02 22:14:52 (194) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-02 22:14:53 (2290) [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-04-02 22:14:53 (305) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-03 22:14:57 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-03 22:15:29 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-03 22:15:29 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6rPWRE8Znx/ea_profile.json * 2024-04-03 22:15:31 (2647) [INFO] Backed up EA4 profile to /tmp/6rPWRE8Znx/ea_profile.json * 2024-04-03 22:15:31 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-03 22:15:32 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-03 22:15:33 (2295) [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-04-03 22:15:33 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-04 22:15:44 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-04 22:16:12 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-04 22:16:12 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jKFtDARXDU/ea_profile.json * 2024-04-04 22:16:13 (2647) [INFO] Backed up EA4 profile to /tmp/jKFtDARXDU/ea_profile.json * 2024-04-04 22:16:14 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-04 22:16:15 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-04 22:16:16 (2295) [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-04-04 22:16:16 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-05 22:14:12 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-05 22:14:41 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-05 22:14:42 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Hdd4KScjBL/ea_profile.json * 2024-04-05 22:14:48 (2647) [INFO] Backed up EA4 profile to /tmp/Hdd4KScjBL/ea_profile.json * 2024-04-05 22:14:49 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-05 22:14:50 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-05 22:14:51 (2295) [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-04-05 22:14:51 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-06 22:15:17 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-06 22:15:45 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-06 22:15:45 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/h8WdFFmxHn/ea_profile.json * 2024-04-06 22:15:47 (2647) [INFO] Backed up EA4 profile to /tmp/h8WdFFmxHn/ea_profile.json * 2024-04-06 22:15:47 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-06 22:15:48 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-06 22:15:49 (2295) [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-04-06 22:15:49 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-07 22:15:02 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-07 22:15:32 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-07 22:15:32 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ddQTQtRUda/ea_profile.json * 2024-04-07 22:15:33 (2647) [INFO] Backed up EA4 profile to /tmp/ddQTQtRUda/ea_profile.json * 2024-04-07 22:15:33 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-07 22:15:34 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-07 22:15:35 (2295) [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-04-07 22:15:35 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-08 22:14:01 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-08 22:14:25 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-08 22:14:25 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cpXm2U9ygs/ea_profile.json * 2024-04-08 22:14:26 (2647) [INFO] Backed up EA4 profile to /tmp/cpXm2U9ygs/ea_profile.json * 2024-04-08 22:14:26 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-08 22:14:27 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-08 22:14:27 (2295) [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-04-08 22:14:27 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-09 22:15:34 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-09 22:16:00 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-09 22:16:00 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0iMFP63S83/ea_profile.json * 2024-04-09 22:16:02 (2647) [INFO] Backed up EA4 profile to /tmp/0iMFP63S83/ea_profile.json * 2024-04-09 22:16:02 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-09 22:16:03 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-09 22:16:04 (2295) [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-04-09 22:16:04 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-10 22:14:11 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-10 22:14:39 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-10 22:14:39 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dhj7Ced0Sh/ea_profile.json * 2024-04-10 22:14:40 (2647) [INFO] Backed up EA4 profile to /tmp/dhj7Ced0Sh/ea_profile.json * 2024-04-10 22:14:40 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-10 22:14:41 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-10 22:14:42 (2295) [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-04-10 22:14:42 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-11 22:14:09 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-11 22:14:36 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-11 22:14:36 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/V9iM8cp7_Z/ea_profile.json * 2024-04-11 22:14:37 (2647) [INFO] Backed up EA4 profile to /tmp/V9iM8cp7_Z/ea_profile.json * 2024-04-11 22:14:37 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-11 22:14:38 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-11 22:14:39 (2295) [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-04-11 22:14:39 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-12 22:14:16 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-12 22:14:43 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-12 22:14:43 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ez0cr21Oxi/ea_profile.json * 2024-04-12 22:14:45 (2647) [INFO] Backed up EA4 profile to /tmp/ez0cr21Oxi/ea_profile.json * 2024-04-12 22:14:45 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-12 22:14:47 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-12 22:14:48 (2295) [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-04-12 22:14:48 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-13 22:15:08 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-13 22:15:33 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-13 22:15:33 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/G2_QYdEZ6j/ea_profile.json * 2024-04-13 22:15:34 (2647) [INFO] Backed up EA4 profile to /tmp/G2_QYdEZ6j/ea_profile.json * 2024-04-13 22:15:34 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-13 22:15:35 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-13 22:15:36 (2295) [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-04-13 22:15:36 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-14 22:14:59 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-14 22:15:26 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-14 22:15:27 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ppOTNMLLBG/ea_profile.json * 2024-04-14 22:15:28 (2647) [INFO] Backed up EA4 profile to /tmp/ppOTNMLLBG/ea_profile.json * 2024-04-14 22:15:28 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-14 22:15:31 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-14 22:15:32 (2295) [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-04-14 22:15:32 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-15 22:14:07 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-15 22:14:34 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-15 22:14:34 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZaVIkWDsBt/ea_profile.json * 2024-04-15 22:14:35 (2647) [INFO] Backed up EA4 profile to /tmp/ZaVIkWDsBt/ea_profile.json * 2024-04-15 22:14:36 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-15 22:14:37 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-15 22:14:37 (2295) [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-04-15 22:14:37 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-16 22:15:16 (6907) [INFO] Self-update of script version 33 requested. * 2024-04-16 22:15:17 (6929) [INFO] Script is up to date. * 2024-04-16 22:15:20 (196) [WARN] *** Elevation Blocker detected: *** You are using MySQL 5.7 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-16 22:15:46 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-16 22:15:46 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PwPDe78jNo/ea_profile.json * 2024-04-16 22:15:47 (2647) [INFO] Backed up EA4 profile to /tmp/PwPDe78jNo/ea_profile.json * 2024-04-16 22:15:47 (196) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-16 22:15:48 (196) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-16 22:15:49 (2295) [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-04-16 22:15:49 (307) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-17 22:14:22 (6907) [INFO] Self-update of script version 33 requested. * 2024-04-17 22:14:23 (6912) [INFO] Newer version of script found. Downloading. * 2024-04-17 22:14:23 (6921) [INFO] Script update to version 34 successful. * 2024-04-17 22:14:26 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-17 22:14:26 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-17 22:14:51 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-17 22:14:51 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_DwVIk5Cgp/ea_profile.json * 2024-04-17 22:14:52 (2664) [INFO] Backed up EA4 profile to /tmp/_DwVIk5Cgp/ea_profile.json * 2024-04-17 22:14:53 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-17 22:14:53 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-17 22:14:54 (2312) [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-04-17 22:14:54 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-18 22:15:44 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-18 22:15:44 (7128) [INFO] Script is up to date. * 2024-04-18 22:15:47 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-18 22:15:47 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-18 22:16:14 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-18 22:16:14 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EcMvjgdDEL/ea_profile.json * 2024-04-18 22:16:15 (2664) [INFO] Backed up EA4 profile to /tmp/EcMvjgdDEL/ea_profile.json * 2024-04-18 22:16:15 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-18 22:16:16 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-18 22:16:17 (2312) [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-04-18 22:16:17 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-19 22:14:59 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-19 22:14:59 (7128) [INFO] Script is up to date. * 2024-04-19 22:15:05 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-19 22:15:05 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-19 22:15:14 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-19 22:15:14 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gaJFYb5Wgx/ea_profile.json * 2024-04-19 22:15:15 (2664) [INFO] Backed up EA4 profile to /tmp/gaJFYb5Wgx/ea_profile.json * 2024-04-19 22:15:15 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-19 22:15:16 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-19 22:15:17 (2312) [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-04-19 22:15:17 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-20 22:16:12 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-20 22:16:12 (7128) [INFO] Script is up to date. * 2024-04-20 22:16:16 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-20 22:16:16 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-20 22:16:42 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-20 22:16:42 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BFgSjkfSaK/ea_profile.json * 2024-04-20 22:16:43 (2664) [INFO] Backed up EA4 profile to /tmp/BFgSjkfSaK/ea_profile.json * 2024-04-20 22:16:43 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-20 22:16:44 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-20 22:16:45 (2312) [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-04-20 22:16:45 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-21 22:14:51 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-21 22:14:52 (7128) [INFO] Script is up to date. * 2024-04-21 22:14:53 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-21 22:14:53 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-21 22:15:21 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-21 22:15:21 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5BiNY_GUmw/ea_profile.json * 2024-04-21 22:15:22 (2664) [INFO] Backed up EA4 profile to /tmp/5BiNY_GUmw/ea_profile.json * 2024-04-21 22:15:22 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-21 22:15:23 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-21 22:15:28 (2312) [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-04-21 22:15:28 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-22 22:14:10 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-22 22:14:10 (7128) [INFO] Script is up to date. * 2024-04-22 22:14:12 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-22 22:14:12 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-22 22:14:39 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-22 22:14:39 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bZALPmUPPm/ea_profile.json * 2024-04-22 22:14:40 (2664) [INFO] Backed up EA4 profile to /tmp/bZALPmUPPm/ea_profile.json * 2024-04-22 22:14:40 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-22 22:14:41 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-22 22:14:42 (2312) [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-04-22 22:14:42 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-23 22:14:45 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-23 22:14:45 (7128) [INFO] Script is up to date. * 2024-04-23 22:14:48 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-23 22:14:48 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-23 22:15:16 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-23 22:15:16 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C_3QobTsWg/ea_profile.json * 2024-04-23 22:15:17 (2664) [INFO] Backed up EA4 profile to /tmp/C_3QobTsWg/ea_profile.json * 2024-04-23 22:15:18 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-23 22:15:19 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-23 22:15:19 (2312) [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-04-23 22:15:19 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-24 22:14:11 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-24 22:14:11 (7128) [INFO] Script is up to date. * 2024-04-24 22:14:13 (712) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-24 22:14:13 (719) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-24 22:14:41 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-24 22:14:41 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2C0AKMc5FP/ea_profile.json * 2024-04-24 22:14:42 (2664) [INFO] Backed up EA4 profile to /tmp/2C0AKMc5FP/ea_profile.json * 2024-04-24 22:14:42 (192) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-24 22:14:43 (192) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-24 22:14:44 (2312) [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-04-24 22:14:44 (303) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-25 22:14:18 (7106) [INFO] Self-update of script version 34 requested. * 2024-04-25 22:14:18 (7111) [INFO] Newer version of script found. Downloading. * 2024-04-25 22:14:19 (7120) [INFO] Script update to version 35 successful. * 2024-04-25 22:14:21 (715) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-25 22:14:21 (722) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-25 22:14:47 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-25 22:14:47 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KVfnQKjodW/ea_profile.json * 2024-04-25 22:14:48 (2782) [INFO] Backed up EA4 profile to /tmp/KVfnQKjodW/ea_profile.json * 2024-04-25 22:14:48 (198) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-25 22:14:49 (198) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-25 22:14:50 (2321) [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-04-25 22:14:50 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-26 22:14:07 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-26 22:14:07 (7138) [INFO] Script is up to date. * 2024-04-26 22:14:09 (715) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-26 22:14:09 (722) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-26 22:14:36 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-26 22:14:36 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KdP_fiPWqy/ea_profile.json * 2024-04-26 22:14:37 (2782) [INFO] Backed up EA4 profile to /tmp/KdP_fiPWqy/ea_profile.json * 2024-04-26 22:14:37 (198) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-26 22:14:38 (198) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-26 22:14:39 (2321) [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-04-26 22:14:39 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-27 22:14:57 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-27 22:14:58 (7138) [INFO] Script is up to date. * 2024-04-27 22:15:00 (715) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-27 22:15:00 (722) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-27 22:15:28 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-27 22:15:28 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QJ3pJtLOqd/ea_profile.json * 2024-04-27 22:15:29 (2782) [INFO] Backed up EA4 profile to /tmp/QJ3pJtLOqd/ea_profile.json * 2024-04-27 22:15:29 (198) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-27 22:15:30 (198) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-27 22:15:30 (2321) [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-04-27 22:15:30 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-28 22:14:59 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-28 22:14:59 (7138) [INFO] Script is up to date. * 2024-04-28 22:15:02 (715) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-28 22:15:02 (722) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-28 22:15:35 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-28 22:15:35 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3JQfhAshE9/ea_profile.json * 2024-04-28 22:15:36 (2782) [INFO] Backed up EA4 profile to /tmp/3JQfhAshE9/ea_profile.json * 2024-04-28 22:15:36 (198) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-28 22:15:37 (198) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-28 22:15:38 (2321) [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-04-28 22:15:38 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-29 22:14:02 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-29 22:14:03 (7138) [INFO] Script is up to date. * 2024-04-29 22:14:04 (715) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-29 22:14:04 (722) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-29 22:14:30 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-29 22:14:30 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TRdxDYazJ6/ea_profile.json * 2024-04-29 22:14:30 (2782) [INFO] Backed up EA4 profile to /tmp/TRdxDYazJ6/ea_profile.json * 2024-04-29 22:14:31 (198) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-29 22:14:31 (198) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-29 22:14:32 (2321) [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-04-29 22:14:32 (309) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-04-30 22:14:01 (7116) [INFO] Self-update of script version 35 requested. * 2024-04-30 22:14:01 (7121) [INFO] Newer version of script found. Downloading. * 2024-04-30 22:14:01 (7130) [INFO] Script update to version 36 successful. * 2024-04-30 22:14:03 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-04-30 22:14:03 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-04-30 22:14:27 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-04-30 22:14:27 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MODX5ZEiVo/ea_profile.json * 2024-04-30 22:14:29 (3173) [INFO] Backed up EA4 profile to /tmp/MODX5ZEiVo/ea_profile.json * 2024-04-30 22:14:29 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-04-30 22:14:29 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04-30 22:14:30 (2313) [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-04-30 22:14:30 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-01 22:15:08 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-01 22:15:09 (7530) [INFO] Script is up to date. * 2024-05-01 22:15:10 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-01 22:15:10 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-01 22:15:20 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-01 22:15:20 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZzJ_yPqupt/ea_profile.json * 2024-05-01 22:15:21 (3173) [INFO] Backed up EA4 profile to /tmp/ZzJ_yPqupt/ea_profile.json * 2024-05-01 22:15:22 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-01 22:15:22 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-01 22:15:23 (2313) [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-05-01 22:15:23 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-02 22:14:27 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-02 22:14:27 (7530) [INFO] Script is up to date. * 2024-05-02 22:14:29 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-02 22:14:29 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-02 22:15:06 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-02 22:15:06 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uLrOKsWuEd/ea_profile.json * 2024-05-02 22:15:07 (3173) [INFO] Backed up EA4 profile to /tmp/uLrOKsWuEd/ea_profile.json * 2024-05-02 22:15:07 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-02 22:15:08 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-02 22:15:09 (2313) [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-05-02 22:15:09 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-03 22:14:04 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-03 22:14:04 (7530) [INFO] Script is up to date. * 2024-05-03 22:14:06 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-03 22:14:06 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-03 22:14:32 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-03 22:14:32 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DiP1d9IIVJ/ea_profile.json * 2024-05-03 22:14:34 (3173) [INFO] Backed up EA4 profile to /tmp/DiP1d9IIVJ/ea_profile.json * 2024-05-03 22:14:34 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-03 22:14:35 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-03 22:14:36 (2313) [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-05-03 22:14:36 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-04 22:14:52 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-04 22:14:52 (7530) [INFO] Script is up to date. * 2024-05-04 22:14:54 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-04 22:14:54 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-04 22:15:21 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-04 22:15:21 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E7M0SjZVS1/ea_profile.json * 2024-05-04 22:15:21 (3173) [INFO] Backed up EA4 profile to /tmp/E7M0SjZVS1/ea_profile.json * 2024-05-04 22:15:22 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-04 22:15:22 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-04 22:15:23 (2313) [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-05-04 22:15:23 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-05 22:15:03 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-05 22:15:04 (7530) [INFO] Script is up to date. * 2024-05-05 22:15:05 (716) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-05 22:15:05 (723) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-05 22:15:33 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-05 22:15:33 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7xp2hYzszT/ea_profile.json * 2024-05-05 22:15:34 (3173) [INFO] Backed up EA4 profile to /tmp/7xp2hYzszT/ea_profile.json * 2024-05-05 22:15:34 (199) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-05 22:15:35 (199) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-05 22:15:36 (2313) [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-05-05 22:15:36 (310) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-06 22:14:23 (7508) [INFO] Self-update of script version 36 requested. * 2024-05-06 22:14:23 (7513) [INFO] Newer version of script found. Downloading. * 2024-05-06 22:14:23 (7522) [INFO] Script update to version 37 successful. * 2024-05-06 22:14:25 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-06 22:14:25 (6322) [INFO] * 2024-05-06 22:14:25 (6352) [INFO] * 2024-05-06 22:14:25 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-06 22:14:25 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-06 22:14:50 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-06 22:14:50 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XSZkyTJ0dw/ea_profile.json * 2024-05-06 22:14:51 (3212) [INFO] Backed up EA4 profile to /tmp/XSZkyTJ0dw/ea_profile.json * 2024-05-06 22:14:52 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-06 22:14:53 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-06 22:14:53 (2352) [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-05-06 22:14:53 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-07 22:14:02 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-07 22:14:02 (7570) [INFO] Script is up to date. * 2024-05-07 22:14:03 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-07 22:14:03 (6322) [INFO] * 2024-05-07 22:14:03 (6352) [INFO] * 2024-05-07 22:14:04 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-07 22:14:04 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-07 22:14:29 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-07 22:14:29 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TszO_uMz57/ea_profile.json * 2024-05-07 22:14:30 (3212) [INFO] Backed up EA4 profile to /tmp/TszO_uMz57/ea_profile.json * 2024-05-07 22:14:30 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-07 22:14:31 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-07 22:14:32 (2352) [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-05-07 22:14:32 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-08 22:14:22 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-08 22:14:22 (7570) [INFO] Script is up to date. * 2024-05-08 22:14:23 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-08 22:14:23 (6322) [INFO] * 2024-05-08 22:14:23 (6352) [INFO] * 2024-05-08 22:14:24 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-08 22:14:24 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-08 22:14:49 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-08 22:14:49 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WvAB7au2_g/ea_profile.json * 2024-05-08 22:14:50 (3212) [INFO] Backed up EA4 profile to /tmp/WvAB7au2_g/ea_profile.json * 2024-05-08 22:14:51 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-08 22:14:52 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-08 22:14:53 (2352) [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-05-08 22:14:53 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-09 22:14:16 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-09 22:14:17 (7570) [INFO] Script is up to date. * 2024-05-09 22:14:17 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-09 22:14:17 (6322) [INFO] * 2024-05-09 22:14:17 (6352) [INFO] * 2024-05-09 22:14:18 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-09 22:14:18 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-09 22:14:40 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-09 22:14:40 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kJghdCgvt9/ea_profile.json * 2024-05-09 22:14:41 (3212) [INFO] Backed up EA4 profile to /tmp/kJghdCgvt9/ea_profile.json * 2024-05-09 22:14:41 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-09 22:14:42 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-09 22:14:43 (2352) [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-05-09 22:14:43 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-10 22:14:00 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-10 22:14:00 (7570) [INFO] Script is up to date. * 2024-05-10 22:14:01 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-10 22:14:01 (6322) [INFO] * 2024-05-10 22:14:01 (6352) [INFO] * 2024-05-10 22:14:02 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-10 22:14:02 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-10 22:14:25 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-10 22:14:25 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mtKDyh2NsA/ea_profile.json * 2024-05-10 22:14:26 (3212) [INFO] Backed up EA4 profile to /tmp/mtKDyh2NsA/ea_profile.json * 2024-05-10 22:14:27 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-10 22:14:28 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-10 22:14:30 (2352) [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-05-10 22:14:30 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-11 22:14:59 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-11 22:14:59 (7570) [INFO] Script is up to date. * 2024-05-11 22:14:59 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-11 22:14:59 (6322) [INFO] * 2024-05-11 22:14:59 (6352) [INFO] * 2024-05-11 22:15:00 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-11 22:15:00 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-11 22:15:24 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-11 22:15:24 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2NudjXpzDu/ea_profile.json * 2024-05-11 22:15:25 (3212) [INFO] Backed up EA4 profile to /tmp/2NudjXpzDu/ea_profile.json * 2024-05-11 22:15:25 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-11 22:15:26 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-11 22:15:27 (2352) [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-05-11 22:15:27 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-12 22:14:58 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-12 22:14:58 (7570) [INFO] Script is up to date. * 2024-05-12 22:14:59 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-12 22:14:59 (6322) [INFO] * 2024-05-12 22:14:59 (6352) [INFO] * 2024-05-12 22:15:00 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-12 22:15:00 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-12 22:15:26 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-12 22:15:27 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dsq6ty6XOk/ea_profile.json * 2024-05-12 22:15:28 (3212) [INFO] Backed up EA4 profile to /tmp/dsq6ty6XOk/ea_profile.json * 2024-05-12 22:15:28 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-12 22:15:31 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-12 22:15:32 (2352) [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-05-12 22:15:32 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-13 22:14:03 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-13 22:14:03 (7570) [INFO] Script is up to date. * 2024-05-13 22:14:04 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-13 22:14:04 (6322) [INFO] * 2024-05-13 22:14:04 (6352) [INFO] * 2024-05-13 22:14:04 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-13 22:14:04 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-13 22:14:29 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-13 22:14:29 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LofaFcibNQ/ea_profile.json * 2024-05-13 22:14:30 (3212) [INFO] Backed up EA4 profile to /tmp/LofaFcibNQ/ea_profile.json * 2024-05-13 22:14:31 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-13 22:14:32 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-13 22:14:37 (2352) [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-05-13 22:14:37 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-14 22:14:01 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-14 22:14:01 (7570) [INFO] Script is up to date. * 2024-05-14 22:14:02 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-14 22:14:02 (6322) [INFO] * 2024-05-14 22:14:02 (6352) [INFO] * 2024-05-14 22:14:02 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-14 22:14:02 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-14 22:14:25 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-14 22:14:25 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fzlyAF5yOY/ea_profile.json * 2024-05-14 22:14:26 (3212) [INFO] Backed up EA4 profile to /tmp/fzlyAF5yOY/ea_profile.json * 2024-05-14 22:14:27 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-14 22:14:27 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-14 22:14:28 (2352) [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-05-14 22:14:28 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-15 22:14:12 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-15 22:14:13 (7570) [INFO] Script is up to date. * 2024-05-15 22:14:14 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr * 2024-05-15 22:14:14 (6322) [INFO] * 2024-05-15 22:14:14 (6352) [INFO] * 2024-05-15 22:14:14 (200) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-15 22:14:14 (719) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-15 22:14:14 (726) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-15 22:14:40 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-15 22:14:40 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TTcUgBtjTr/ea_profile.json * 2024-05-15 22:14:41 (3212) [INFO] Backed up EA4 profile to /tmp/TTcUgBtjTr/ea_profile.json * 2024-05-15 22:14:41 (200) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime - ea-php71 - ea-php71-libc-client - ea-php71-pear - ea-php71-php-bcmath - ea-php71-php-calendar - ea-php71-php-cli - ea-php71-php-common - ea-php71-php-curl - ea-php71-php-devel - ea-php71-php-fpm - ea-php71-php-ftp - ea-php71-php-gd - ea-php71-php-gettext - ea-php71-php-iconv - ea-php71-php-imap - ea-php71-php-ioncube10 - ea-php71-php-litespeed - ea-php71-php-mbstring - ea-php71-php-mcrypt - ea-php71-php-mysqlnd - ea-php71-php-pdo - ea-php71-php-posix - ea-php71-php-sockets - ea-php71-php-xml - ea-php71-runtime * 2024-05-15 22:14:42 (200) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-15 22:14:43 (2352) [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-05-15 22:14:43 (313) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-16 22:15:34 (7548) [INFO] Self-update of script version 37 requested. * 2024-05-16 22:15:34 (7553) [INFO] Newer version of script found. Downloading. * 2024-05-16 22:15:35 (7562) [INFO] Script update to version 38 successful. * 2024-05-16 22:15:36 (201) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-16 22:15:36 (720) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-16 22:15:36 (727) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-16 22:16:04 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-16 22:16:04 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JJ2xogV0jp/ea_profile.json * 2024-05-16 22:16:05 (5705) [INFO] Backed up EA4 profile to /tmp/JJ2xogV0jp/ea_profile.json * 2024-05-16 22:16:07 (201) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-05-16 22:16:08 (201) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-16 22:16:14 (2459) [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-05-16 22:16:14 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-17 22:14:22 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-17 22:14:22 (7748) [INFO] Script is up to date. * 2024-05-17 22:14:23 (201) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-17 22:14:24 (720) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-17 22:14:24 (727) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-17 22:14:48 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-17 22:14:48 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CsaJDGB2Aa/ea_profile.json * 2024-05-17 22:14:49 (5705) [INFO] Backed up EA4 profile to /tmp/CsaJDGB2Aa/ea_profile.json * 2024-05-17 22:14:51 (201) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-05-17 22:14:52 (201) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-17 22:14:53 (2459) [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-05-17 22:14:53 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-18 22:14:52 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-18 22:14:53 (7748) [INFO] Script is up to date. * 2024-05-18 22:14:54 (201) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-18 22:14:54 (720) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-18 22:14:54 (727) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-18 22:15:17 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-18 22:15:18 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bGAcXbOm2X/ea_profile.json * 2024-05-18 22:15:19 (5705) [INFO] Backed up EA4 profile to /tmp/bGAcXbOm2X/ea_profile.json * 2024-05-18 22:15:20 (201) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-05-18 22:15:21 (201) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-18 22:15:22 (2459) [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-05-18 22:15:22 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-19 22:15:09 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-19 22:15:09 (7748) [INFO] Script is up to date. * 2024-05-19 22:15:11 (201) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-19 22:15:12 (720) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-19 22:15:12 (727) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-19 22:15:53 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-19 22:15:53 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XNmVVcsIF3/ea_profile.json * 2024-05-19 22:15:54 (5705) [INFO] Backed up EA4 profile to /tmp/XNmVVcsIF3/ea_profile.json * 2024-05-19 22:15:57 (201) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-05-19 22:16:03 (201) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-19 22:16:03 (2459) [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-05-19 22:16:03 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-05-20 22:14:23 (7726) [INFO] Self-update of script version 38 requested. * 2024-05-20 22:14:23 (7748) [INFO] Script is up to date. * 2024-05-20 22:14:24 (201) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-05-20 22:14:25 (720) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-05-20 22:14:25 (727) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-05-20 22:14:51 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-05-20 22:14:52 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PJWXZofll6/ea_profile.json * 2024-05-20 22:14:55 (5705) [INFO] Backed up EA4 profile to /tmp/PJWXZofll6/ea_profile.json * 2024-05-20 22:14:58 (201) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-05-20 22:14:59 (201) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05-20 22:15:00 (2459) [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-05-20 22:15:00 (314) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-02 22:17:41 (7726) [INFO] Self-update of script version 38 requested. * 2024-06-02 22:17:41 (7731) [INFO] Newer version of script found. Downloading. * 2024-06-02 22:17:42 (7740) [INFO] Script update to version 39 successful. * 2024-06-02 22:17:44 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-02 22:17:44 (6568) [INFO] * 2024-06-02 22:17:48 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:17:48 (6598) [INFO] * 2024-06-02 22:17:48 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-02 22:17:48 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-02 22:17:55 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-02 22:17:55 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/90n5DvxLy6/ea_profile.json * 2024-06-02 22:17:56 (5773) [INFO] Backed up EA4 profile to /tmp/90n5DvxLy6/ea_profile.json * 2024-06-02 22:17:57 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-02 22:17:58 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-02 22:17:58 (2508) [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-02 22:17:58 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-03 22:14:11 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-03 22:14:11 (7817) [INFO] Script is up to date. * 2024-06-03 22:14:12 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-03 22:14:12 (6568) [INFO] * 2024-06-03 22:14:13 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:13 (6598) [INFO] * 2024-06-03 22:14:14 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-03 22:14:14 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-03 22:14:38 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-03 22:14:38 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_KpviHsNut/ea_profile.json * 2024-06-03 22:14:38 (5773) [INFO] Backed up EA4 profile to /tmp/_KpviHsNut/ea_profile.json * 2024-06-03 22:14:40 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-03 22:14:41 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-03 22:14:42 (2508) [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-03 22:14:42 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-04 22:14:02 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-04 22:14:02 (7817) [INFO] Script is up to date. * 2024-06-04 22:14:03 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-04 22:14:03 (6568) [INFO] * 2024-06-04 22:14:06 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:07 (6598) [INFO] * 2024-06-04 22:14:07 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-04 22:14:07 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-04 22:14:30 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-04 22:14:30 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9enzr95SiB/ea_profile.json * 2024-06-04 22:14:31 (5773) [INFO] Backed up EA4 profile to /tmp/9enzr95SiB/ea_profile.json * 2024-06-04 22:14:33 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-04 22:14:33 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-04 22:14:34 (2508) [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-04 22:14:34 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-05 22:14:33 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-05 22:14:33 (7817) [INFO] Script is up to date. * 2024-06-05 22:14:34 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-05 22:14:34 (6568) [INFO] * 2024-06-05 22:14:38 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:38 (6598) [INFO] * 2024-06-05 22:14:39 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-05 22:14:39 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-05 22:15:05 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-05 22:15:05 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uVf7YCQp4U/ea_profile.json * 2024-06-05 22:15:06 (5773) [INFO] Backed up EA4 profile to /tmp/uVf7YCQp4U/ea_profile.json * 2024-06-05 22:15:09 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-05 22:15:10 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-05 22:15:11 (2508) [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-05 22:15:11 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-06 22:14:14 (7795) [INFO] Self-update of script version 39 requested. * 2024-06-06 22:14:14 (7800) [INFO] Newer version of script found. Downloading. * 2024-06-06 22:14:15 (7809) [INFO] Script update to version 40 successful. * 2024-06-06 22:14:16 (124) [ERROR] Tried to sync version /etc/cpanel/TIERS.json file but failed: Signature verification failed for URL 'http://httpupdate.cpanel.net/cpanelsync/TIERS.json'. Could not find public key in keychain. (/var/tmp/26099._USR_LOCAL_CPANEL_SCRIPTS_ELEVATE_CPANEL__.84ac1c42.tmp) Please see https://go.cpanel.net/sigerrors for further information about this error. * 2024-06-06 22:14:16 (353) [WARN] Unknown error while checking blockers: Can't use an undefined value as a HASH reference at /usr/local/cpanel/scripts/elevate-cpanel line 2351. * 2024-06-06 22:14:16 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-07 22:14:06 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-07 22:14:06 (7829) [INFO] Script is up to date. * 2024-06-07 22:14:07 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-07 22:14:07 (6580) [INFO] * 2024-06-07 22:14:09 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:09 (6610) [INFO] * 2024-06-07 22:14:10 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-07 22:14:10 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-07 22:14:34 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-07 22:14:34 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iHTpCupZho/ea_profile.json * 2024-06-07 22:14:34 (5785) [INFO] Backed up EA4 profile to /tmp/iHTpCupZho/ea_profile.json * 2024-06-07 22:14:36 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-07 22:14:37 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-07 22:14:38 (2520) [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-07 22:14:38 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-08 22:14:53 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-08 22:14:53 (7829) [INFO] Script is up to date. * 2024-06-08 22:14:54 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-08 22:14:54 (6580) [INFO] * 2024-06-08 22:14:57 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:58 (6610) [INFO] * 2024-06-08 22:14:58 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-08 22:14:58 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-08 22:15:23 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-08 22:15:23 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uVKWNgzLDD/ea_profile.json * 2024-06-08 22:15:24 (5785) [INFO] Backed up EA4 profile to /tmp/uVKWNgzLDD/ea_profile.json * 2024-06-08 22:15:25 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-08 22:15:26 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-08 22:15:27 (2520) [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-08 22:15:27 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-09 22:14:50 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-09 22:14:50 (7829) [INFO] Script is up to date. * 2024-06-09 22:14:51 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-09 22:14:51 (6580) [INFO] * 2024-06-09 22:14:54 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:54 (6610) [INFO] * 2024-06-09 22:14:54 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-09 22:14:54 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-09 22:15:17 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-09 22:15:17 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2KRdZw7pzg/ea_profile.json * 2024-06-09 22:15:18 (5785) [INFO] Backed up EA4 profile to /tmp/2KRdZw7pzg/ea_profile.json * 2024-06-09 22:15:20 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-09 22:15:20 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-09 22:15:21 (2520) [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-09 22:15:21 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-10 22:14:05 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-10 22:14:05 (7829) [INFO] Script is up to date. * 2024-06-10 22:14:06 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-10 22:14:06 (6580) [INFO] * 2024-06-10 22:14:11 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:11 (6610) [INFO] * 2024-06-10 22:14:11 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-10 22:14:11 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-10 22:14:35 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-10 22:14:35 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EiNVVOvRxg/ea_profile.json * 2024-06-10 22:14:36 (5785) [INFO] Backed up EA4 profile to /tmp/EiNVVOvRxg/ea_profile.json * 2024-06-10 22:14:38 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-10 22:14:40 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-10 22:14:45 (2520) [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-10 22:14:45 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-11 22:14:28 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-11 22:14:28 (7829) [INFO] Script is up to date. * 2024-06-11 22:14:29 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-11 22:14:29 (6580) [INFO] * 2024-06-11 22:14:33 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:33 (6610) [INFO] * 2024-06-11 22:14:34 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-11 22:14:34 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-11 22:14:57 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-11 22:14:57 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l5yUl7i0ge/ea_profile.json * 2024-06-11 22:14:58 (5785) [INFO] Backed up EA4 profile to /tmp/l5yUl7i0ge/ea_profile.json * 2024-06-11 22:14:59 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-11 22:15:01 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-11 22:15:02 (2520) [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-11 22:15:02 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-12 22:16:47 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-12 22:16:47 (7829) [INFO] Script is up to date. * 2024-06-12 22:16:49 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-12 22:16:49 (6580) [INFO] * 2024-06-12 22:16:55 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:16:55 (6610) [INFO] * 2024-06-12 22:16:56 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-12 22:16:56 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-12 22:17:03 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-12 22:17:03 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5Bca9CQzny/ea_profile.json * 2024-06-12 22:17:04 (5785) [INFO] Backed up EA4 profile to /tmp/5Bca9CQzny/ea_profile.json * 2024-06-12 22:17:06 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-12 22:17:07 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-12 22:17:07 (2520) [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-12 22:17:07 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-13 22:14:24 (7807) [INFO] Self-update of script version 40 requested. * 2024-06-13 22:14:24 (7812) [INFO] Newer version of script found. Downloading. * 2024-06-13 22:14:25 (7821) [INFO] Script update to version 41 successful. * 2024-06-13 22:14:26 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-13 22:14:26 (6591) [INFO] * 2024-06-13 22:14:28 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:29 (6621) [INFO] * 2024-06-13 22:14:29 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-13 22:14:29 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-13 22:14:56 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-13 22:14:56 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2ZkNASsQXP/ea_profile.json * 2024-06-13 22:14:57 (5796) [INFO] Backed up EA4 profile to /tmp/2ZkNASsQXP/ea_profile.json * 2024-06-13 22:14:58 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-13 22:14:59 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-13 22:15:00 (2531) [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-13 22:15:00 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-14 22:14:14 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-14 22:14:14 (7840) [INFO] Script is up to date. * 2024-06-14 22:14:15 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-14 22:14:15 (6591) [INFO] * 2024-06-14 22:14:18 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:18 (6621) [INFO] * 2024-06-14 22:14:19 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-14 22:14:19 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-14 22:14:42 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-14 22:14:42 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l1d6dKl80O/ea_profile.json * 2024-06-14 22:14:43 (5796) [INFO] Backed up EA4 profile to /tmp/l1d6dKl80O/ea_profile.json * 2024-06-14 22:14:44 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-14 22:14:45 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-14 22:14:46 (2531) [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-14 22:14:46 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-15 22:15:05 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-15 22:15:05 (7840) [INFO] Script is up to date. * 2024-06-15 22:15:06 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-15 22:15:06 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-15 22:15:06 (6591) [INFO] * 2024-06-15 22:15:09 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:15:10 (6621) [INFO] * 2024-06-15 22:15:10 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-15 22:15:10 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-15 22:15:33 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-15 22:15:33 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xxAO3o_tdx/ea_profile.json * 2024-06-15 22:15:35 (5796) [INFO] Backed up EA4 profile to /tmp/xxAO3o_tdx/ea_profile.json * 2024-06-15 22:15:37 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-15 22:15:37 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-15 22:15:38 (2531) [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-15 22:15:38 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-16 22:14:56 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-16 22:14:56 (7840) [INFO] Script is up to date. * 2024-06-16 22:14:57 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-16 22:14:57 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-16 22:14:57 (6591) [INFO] * 2024-06-16 22:15:01 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:15:01 (6621) [INFO] * 2024-06-16 22:15:02 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-16 22:15:02 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-16 22:15:26 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-16 22:15:26 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_pt_ZVDS8A/ea_profile.json * 2024-06-16 22:15:28 (5796) [INFO] Backed up EA4 profile to /tmp/_pt_ZVDS8A/ea_profile.json * 2024-06-16 22:15:32 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-16 22:15:33 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-16 22:15:33 (2531) [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-16 22:15:33 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-17 22:14:02 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-17 22:14:02 (7840) [INFO] Script is up to date. * 2024-06-17 22:14:03 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-17 22:14:03 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-17 22:14:03 (6591) [INFO] * 2024-06-17 22:14:06 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:06 (6621) [INFO] * 2024-06-17 22:14:06 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-17 22:14:06 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-17 22:14:30 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-17 22:14:30 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XlVXoPn0gH/ea_profile.json * 2024-06-17 22:14:32 (5796) [INFO] Backed up EA4 profile to /tmp/XlVXoPn0gH/ea_profile.json * 2024-06-17 22:14:34 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-17 22:14:35 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-17 22:14:39 (2531) [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-17 22:14:39 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-18 22:14:15 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-18 22:14:15 (7840) [INFO] Script is up to date. * 2024-06-18 22:14:16 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-18 22:14:16 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-18 22:14:16 (6591) [INFO] * 2024-06-18 22:14:22 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:22 (6621) [INFO] * 2024-06-18 22:14:22 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-18 22:14:22 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-18 22:14:46 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-18 22:14:46 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AGmpegwvRm/ea_profile.json * 2024-06-18 22:14:47 (5796) [INFO] Backed up EA4 profile to /tmp/AGmpegwvRm/ea_profile.json * 2024-06-18 22:14:49 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-18 22:14:55 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-18 22:14:56 (2531) [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-18 22:14:56 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-19 22:14:22 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-19 22:14:22 (7840) [INFO] Script is up to date. * 2024-06-19 22:14:23 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-19 22:14:23 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-19 22:14:23 (6591) [INFO] * 2024-06-19 22:14:24 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:24 (6621) [INFO] * 2024-06-19 22:14:24 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-19 22:14:24 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-19 22:14:47 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-19 22:14:47 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OXWUOCl4YO/ea_profile.json * 2024-06-19 22:14:48 (5796) [INFO] Backed up EA4 profile to /tmp/OXWUOCl4YO/ea_profile.json * 2024-06-19 22:14:49 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-19 22:14:50 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-19 22:14:51 (2531) [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-19 22:14:51 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-20 22:14:31 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-20 22:14:31 (7840) [INFO] Script is up to date. * 2024-06-20 22:14:32 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-20 22:14:32 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-20 22:14:32 (6591) [INFO] * 2024-06-20 22:14:37 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:37 (6621) [INFO] * 2024-06-20 22:14:38 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-20 22:14:38 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-20 22:15:01 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-20 22:15:01 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vKFihzrGp4/ea_profile.json * 2024-06-20 22:15:03 (5796) [INFO] Backed up EA4 profile to /tmp/vKFihzrGp4/ea_profile.json * 2024-06-20 22:15:05 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-20 22:15:06 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-20 22:15:06 (2531) [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-20 22:15:06 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-21 22:14:07 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-21 22:14:07 (7840) [INFO] Script is up to date. * 2024-06-21 22:14:09 (202) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-06-21 22:14:09 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-21 22:14:09 (6591) [INFO] * 2024-06-21 22:14:12 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:13 (6621) [INFO] * 2024-06-21 22:14:13 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-21 22:14:13 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-21 22:14:38 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-21 22:14:38 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/COii9WjaXX/ea_profile.json * 2024-06-21 22:14:39 (5796) [INFO] Backed up EA4 profile to /tmp/COii9WjaXX/ea_profile.json * 2024-06-21 22:14:41 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-21 22:14:42 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-21 22:14:43 (2531) [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-21 22:14:43 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-22 22:16:07 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-22 22:16:07 (7840) [INFO] Script is up to date. * 2024-06-22 22:16:08 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-22 22:16:08 (6591) [INFO] * 2024-06-22 22:16:11 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:16:11 (6621) [INFO] * 2024-06-22 22:16:12 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-22 22:16:12 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-22 22:16:37 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-22 22:16:37 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NDQSqBjH0J/ea_profile.json * 2024-06-22 22:16:38 (5796) [INFO] Backed up EA4 profile to /tmp/NDQSqBjH0J/ea_profile.json * 2024-06-22 22:16:40 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-22 22:16:41 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-22 22:16:43 (2531) [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-22 22:16:43 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-23 22:15:05 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-23 22:15:05 (7840) [INFO] Script is up to date. * 2024-06-23 22:15:06 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-23 22:15:06 (6591) [INFO] * 2024-06-23 22:15:10 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:15:10 (6621) [INFO] * 2024-06-23 22:15:11 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-23 22:15:11 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-23 22:15:44 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-23 22:15:44 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NJQlARIzFX/ea_profile.json * 2024-06-23 22:15:46 (5796) [INFO] Backed up EA4 profile to /tmp/NJQlARIzFX/ea_profile.json * 2024-06-23 22:15:48 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-23 22:15:49 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-23 22:15:50 (2531) [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-23 22:15:50 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-24 22:14:18 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-24 22:14:18 (7840) [INFO] Script is up to date. * 2024-06-24 22:14:19 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-24 22:14:19 (6591) [INFO] * 2024-06-24 22:14:22 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:22 (6621) [INFO] * 2024-06-24 22:14:23 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-24 22:14:23 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-24 22:14:47 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-24 22:14:47 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Dk8bF1ByYM/ea_profile.json * 2024-06-24 22:14:48 (5796) [INFO] Backed up EA4 profile to /tmp/Dk8bF1ByYM/ea_profile.json * 2024-06-24 22:14:51 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-24 22:14:52 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-24 22:14:56 (2531) [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-24 22:14:56 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-25 22:14:16 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-25 22:14:16 (7840) [INFO] Script is up to date. * 2024-06-25 22:14:17 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-25 22:14:17 (6591) [INFO] * 2024-06-25 22:14:24 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:24 (6621) [INFO] * 2024-06-25 22:14:24 (723) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-25 22:14:24 (730) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-25 22:14:48 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-25 22:14:48 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1EamFvHZt8/ea_profile.json * 2024-06-25 22:14:49 (5796) [INFO] Backed up EA4 profile to /tmp/1EamFvHZt8/ea_profile.json * 2024-06-25 22:14:51 (202) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-25 22:14:52 (202) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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-25 22:14:53 (2531) [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-25 22:14:53 (317) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-26 22:14:50 (7818) [INFO] Self-update of script version 41 requested. * 2024-06-26 22:14:51 (7823) [INFO] Newer version of script found. Downloading. * 2024-06-26 22:14:51 (7832) [INFO] Script update to version 42 successful. * 2024-06-26 22:14:54 (6742) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-26 22:14:54 (6743) [INFO] * 2024-06-26 22:14:59 (6756) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 9, "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 22:14:59 (6773) [INFO] * 2024-06-26 22:14:59 (726) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-26 22:14:59 (733) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-26 22:15:22 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-26 22:15:22 (5886) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3fNQ7waEGR/ea_profile.json * 2024-06-26 22:15:23 (5909) [INFO] Backed up EA4 profile to /tmp/3fNQ7waEGR/ea_profile.json * 2024-06-26 22:15:25 (207) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-26 22:15:26 (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-26 22:15:27 (2556) [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-26 22:15:27 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-27 22:14:08 (7977) [INFO] Self-update of script version 42 requested. * 2024-06-27 22:14:08 (7982) [INFO] Newer version of script found. Downloading. * 2024-06-27 22:14:09 (7991) [INFO] Script update to version 43 successful. * 2024-06-27 22:14:09 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-27 22:14:09 (6738) [INFO] * 2024-06-27 22:14:12 (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": 9, "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 22:14:12 (6768) [INFO] * 2024-06-27 22:14:13 (726) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-27 22:14:13 (733) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-27 22:14:35 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-27 22:14:36 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8GPzbBYRwJ/ea_profile.json * 2024-06-27 22:14:37 (5904) [INFO] Backed up EA4 profile to /tmp/8GPzbBYRwJ/ea_profile.json * 2024-06-27 22:14:37 (207) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-27 22:14: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-27 22:14: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-27 22:14:39 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-28 22:14:09 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-28 22:14:09 (7994) [INFO] Script is up to date. * 2024-06-28 22:14:10 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-28 22:14:10 (6738) [INFO] * 2024-06-28 22:14:15 (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": 9, "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 22:14:15 (6768) [INFO] * 2024-06-28 22:14:16 (726) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-28 22:14:16 (733) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-28 22:14:39 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-28 22:14:40 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x5PgYJhysY/ea_profile.json * 2024-06-28 22:14:41 (5904) [INFO] Backed up EA4 profile to /tmp/x5PgYJhysY/ea_profile.json * 2024-06-28 22:14:41 (207) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-28 22:14:43 (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 22:14:47 (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 22:14:47 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-29 22:14:55 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-29 22:14:55 (7994) [INFO] Script is up to date. * 2024-06-29 22:14:56 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-29 22:14:56 (6738) [INFO] * 2024-06-29 22:15:00 (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": 9, "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 22:15:01 (6768) [INFO] * 2024-06-29 22:15:02 (726) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-29 22:15:02 (733) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-29 22:15:25 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-29 22:15:26 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kDYu0SEo03/ea_profile.json * 2024-06-29 22:15:27 (5904) [INFO] Backed up EA4 profile to /tmp/kDYu0SEo03/ea_profile.json * 2024-06-29 22:15:28 (207) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-29 22:15:29 (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 22:15:29 (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 22:15:29 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-06-30 22:14:57 (7972) [INFO] Self-update of script version 43 requested. * 2024-06-30 22:14:57 (7994) [INFO] Script is up to date. * 2024-06-30 22:14:58 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-06-30 22:14:58 (6738) [INFO] * 2024-06-30 22:15:03 (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": 9, "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 22:15:03 (6768) [INFO] * 2024-06-30 22:15:04 (726) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-06-30 22:15:04 (733) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-06-30 22:15:28 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-06-30 22:15:29 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VtdHxP0sVH/ea_profile.json * 2024-06-30 22:15:30 (5904) [INFO] Backed up EA4 profile to /tmp/VtdHxP0sVH/ea_profile.json * 2024-06-30 22:15:30 (207) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-06-30 22:15:31 (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 22:15:32 (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 22:15:32 (320) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-01 22:16:17 (7972) [INFO] Self-update of script version 43 requested. * 2024-07-01 22:16:17 (7977) [INFO] Newer version of script found. Downloading. * 2024-07-01 22:16:18 (7986) [INFO] Script update to version 44 successful. * 2024-07-01 22:16:20 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-01 22:16:20 (6800) [INFO] * 2024-07-01 22:16:25 (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": 9, "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 22:16:25 (6830) [INFO] * 2024-07-01 22:16:26 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-01 22:16:26 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-01 22:16:50 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-01 22:16:52 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7U9nuzo3fo/ea_profile.json * 2024-07-01 22:16:53 (5966) [INFO] Backed up EA4 profile to /tmp/7U9nuzo3fo/ea_profile.json * 2024-07-01 22:16:53 (208) [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-php56 - ea-php56-libc-client - ea-php56-pear - ea-php56-php-bcmath - ea-php56-php-calendar - ea-php56-php-cli - ea-php56-php-common - ea-php56-php-curl - ea-php56-php-devel - ea-php56-php-fpm - ea-php56-php-ftp - ea-php56-php-gd - ea-php56-php-gettext - ea-php56-php-iconv - ea-php56-php-imap - ea-php56-php-litespeed - ea-php56-php-mbstring - ea-php56-php-mysqlnd - ea-php56-php-pdo - ea-php56-php-posix - ea-php56-php-sockets - ea-php56-php-xml - ea-php56-runtime * 2024-07-01 22:16:55 (208) [WARN] *** Elevation Blocker detected: *** We have detected that your server is hosted by "OVH SA" company. Before continuing the elevation process, you should disable the "proactive monitoring" provided by OVH. When using "proactive monitoring" your server could incorrectly boot in rescue mode during the elevate process. Once you have disabled the monitoring system (or confirm this message does not apply to you), please touch that file and continue the elevation pricess. > touch /var/cpanel/acknowledge_ovh_monitoring_for_elevate You can read more about this issue: URL: https://github.com/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 22:16:59 (2533) [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 22:16:59 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-02 22:13:49 (8035) [INFO] Self-update of script version 44 requested. * 2024-07-02 22:13:49 (8057) [INFO] Script is up to date. * 2024-07-02 22:13:50 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-02 22:13:50 (6800) [INFO] * 2024-07-02 22:13:54 (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": 9, "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 22:13:54 (6830) [INFO] * 2024-07-02 22:13:55 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-02 22:13:55 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-02 22:13:56 (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 22:13:56 (1987) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-02 22:13:56 (6799) [INFO] Running: /usr/bin/yum clean all * 2024-07-02 22:13:56 (6800) [INFO] * 2024-07-02 22:13:56 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-02 22:13:56 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-07-02 22:13:56 (6813) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-07-02 22:13:56 (6813) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-07-02 22:13:56 (6813) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-07-02 22:13:56 (6813) [INFO] : mysql-connectors-community mysql-tools-community * 2024-07-02 22:13:56 (6813) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-07-02 22:13:56 (6813) [INFO] : wp-toolkit-thirdparties * 2024-07-02 22:13:56 (6813) [INFO] Cleaning up list of fastest mirrors * 2024-07-02 22:13:56 (6813) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-07-02 22:13:56 (6830) [INFO] * 2024-07-02 22:14:00 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-02 22:14:00 (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 22:14:01 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-02 22:14:02 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FBgWM1YcEz/ea_profile.json * 2024-07-02 22:14:03 (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/FBgWM1YcEz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945. * 2024-07-02 22:14:03 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-03 22:13:44 (8035) [INFO] Self-update of script version 44 requested. * 2024-07-03 22:13:44 (8057) [INFO] Script is up to date. * 2024-07-03 22:13:46 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-03 22:13:46 (6800) [INFO] * 2024-07-03 22:13: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": 9, "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 22:13:49 (6830) [INFO] * 2024-07-03 22:13:50 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-03 22:13:50 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-03 22:13:52 (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 22:13:52 (1987) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-03 22:13:52 (6799) [INFO] Running: /usr/bin/yum clean all * 2024-07-03 22:13:52 (6800) [INFO] * 2024-07-03 22:13:52 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-03 22:13:53 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel * 2024-07-03 22:13:53 (6813) [INFO] : extras imunify360 imunify360-rollout-1 imunify360-rollout-2 * 2024-07-03 22:13:53 (6813) [INFO] : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5 * 2024-07-03 22:13:53 (6813) [INFO] : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8 * 2024-07-03 22:13:53 (6813) [INFO] : mysql-connectors-community mysql-tools-community * 2024-07-03 22:13:53 (6813) [INFO] : mysql57-community updates wp-toolkit-cpanel * 2024-07-03 22:13:53 (6813) [INFO] : wp-toolkit-thirdparties * 2024-07-03 22:13:53 (6813) [INFO] Cleaning up list of fastest mirrors * 2024-07-03 22:13:53 (6813) [INFO] Other repos take up 2.0 M of disk space (use --verbose for details) * 2024-07-03 22:13:53 (6830) [INFO] * 2024-07-03 22:13:55 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-03 22:13:55 (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 22:13:56 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-03 22:13:57 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RTRvRECwBK/ea_profile.json * 2024-07-03 22:13: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/RTRvRECwBK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945. * 2024-07-03 22:13:59 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-04 22:13:50 (8035) [INFO] Self-update of script version 44 requested. * 2024-07-04 22:13:50 (8040) [INFO] Newer version of script found. Downloading. * 2024-07-04 22:13:50 (8049) [INFO] Script update to version 45 successful. * 2024-07-04 22:13:51 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-04 22:13:51 (6814) [INFO] * 2024-07-04 22:13:56 (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": 9, "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 22:13:56 (6844) [INFO] * 2024-07-04 22:13:57 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-04 22:13:57 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-04 22:13:59 (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 22:13:59 (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 22:13:59 (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 22:13:59 (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 22:13:59 (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 22:13:59 (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 22:14:01 (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 22:14:01 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-04 22:14:01 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-04 22:14:01 (6814) [INFO] * 2024-07-04 22:14:01 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-04 22:14:01 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-04 22:14:01 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-04 22:14:01 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-04 22:14:01 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-04 22:14:01 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-04 22:14:01 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-04 22:14:01 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-04 22:14:01 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-04 22:14:01 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-04 22:14:01 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-04 22:14:01 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-04 22:14:01 (6844) [INFO] * 2024-07-04 22:14:04 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-04 22:14:04 (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 22:14:04 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-04 22:14:05 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3Qv_x_0wxS/ea_profile.json * 2024-07-04 22:14: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/3Qv_x_0wxS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-04 22:14:06 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-05 22:13:46 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-05 22:13:46 (8071) [INFO] Script is up to date. * 2024-07-05 22:13:47 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-05 22:13:47 (6814) [INFO] * 2024-07-05 22:13:51 (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": 9, "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 22:13:51 (6844) [INFO] * 2024-07-05 22:13:51 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-05 22:13:51 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-05 22:13:53 (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 22:13:53 (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 22:13:53 (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 22:13:53 (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 22:13:53 (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 22:13:53 (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 22:13:54 (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 22:13:54 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-05 22:13:54 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-05 22:13:54 (6814) [INFO] * 2024-07-05 22:13:54 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-05 22:13:55 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-05 22:13:55 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-05 22:13:55 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-05 22:13:55 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-05 22:13:55 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-05 22:13:55 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-05 22:13:55 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-05 22:13:55 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-05 22:13:55 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-05 22:13:55 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-05 22:13:55 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-05 22:13:55 (6844) [INFO] * 2024-07-05 22:13:59 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-05 22:13: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 22:14:00 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-05 22:14:01 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zunR8eRQEH/ea_profile.json * 2024-07-05 22:14: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/zunR8eRQEH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-05 22:14:02 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-06 22:14:38 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-06 22:14:38 (8071) [INFO] Script is up to date. * 2024-07-06 22:14:39 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-06 22:14:39 (6814) [INFO] * 2024-07-06 22:14:43 (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": 9, "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 22:14:43 (6844) [INFO] * 2024-07-06 22:14:44 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-06 22:14:44 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-06 22:14:46 (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 22:14:46 (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 22:14:46 (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 22:14:46 (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 22:14:46 (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 22:14:46 (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 22:14: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-06 22:14:48 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-06 22:14:48 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-06 22:14:48 (6814) [INFO] * 2024-07-06 22:14:48 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-06 22:14:48 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-06 22:14:48 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-06 22:14:48 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-06 22:14:48 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-06 22:14:48 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-06 22:14:48 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-06 22:14:48 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-06 22:14:48 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-06 22:14:48 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-06 22:14:48 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-06 22:14:48 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-06 22:14:48 (6844) [INFO] * 2024-07-06 22:14:51 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-06 22:14:51 (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 22:14:51 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-06 22:14:52 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y_OH6ItDhe/ea_profile.json * 2024-07-06 22:14:55 (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/Y_OH6ItDhe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-06 22:14:55 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-07 22:14:29 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-07 22:14:29 (8071) [INFO] Script is up to date. * 2024-07-07 22:14:30 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-07 22:14:30 (6814) [INFO] * 2024-07-07 22:14:33 (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": 9, "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 22:14:33 (6844) [INFO] * 2024-07-07 22:14:34 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-07 22:14:34 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-07 22:14:36 (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 22:14:36 (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 22:14:36 (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 22:14:36 (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 22:14:36 (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 22:14:36 (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 22:14:37 (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 22:14:37 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-07 22:14:37 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-07 22:14:37 (6814) [INFO] * 2024-07-07 22:14:37 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-07 22:14:37 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-07 22:14:37 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-07 22:14:37 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-07 22:14:37 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-07 22:14:37 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-07 22:14:37 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-07 22:14:37 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-07 22:14:37 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-07 22:14:37 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-07 22:14:37 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-07 22:14:38 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-07 22:14:38 (6844) [INFO] * 2024-07-07 22:14:39 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-07 22:14:39 (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 22:14:40 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-07 22:14:40 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MBhWTVAI45/ea_profile.json * 2024-07-07 22:14:41 (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/MBhWTVAI45/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-07 22:14:41 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-08 22:13:41 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-08 22:13:41 (8071) [INFO] Script is up to date. * 2024-07-08 22:13:42 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-08 22:13:42 (6814) [INFO] * 2024-07-08 22:13:44 (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": 9, "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 22:13:44 (6844) [INFO] * 2024-07-08 22:13:44 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-08 22:13:44 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-08 22:13:46 (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 22:13:46 (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 22:13:46 (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 22:13:46 (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 22:13:46 (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 22:13:46 (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 22:13: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 22:13:48 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-08 22:13:48 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-08 22:13:48 (6814) [INFO] * 2024-07-08 22:13:48 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-08 22:13:49 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-08 22:13:49 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-08 22:13:49 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-08 22:13:49 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-08 22:13:49 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-08 22:13:49 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-08 22:13:49 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-08 22:13:49 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-08 22:13:49 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-08 22:13:49 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-08 22:13:49 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-08 22:13:49 (6844) [INFO] * 2024-07-08 22:13:51 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-08 22:13:51 (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 22:13:51 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-08 22:13:52 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nyAEd6S0Ms/ea_profile.json * 2024-07-08 22:13:54 (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/nyAEd6S0Ms/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-08 22:13:54 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-09 22:13:41 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-09 22:13:41 (8071) [INFO] Script is up to date. * 2024-07-09 22:13:42 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-09 22:13:42 (6814) [INFO] * 2024-07-09 22:13:44 (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": 9, "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 22:13:45 (6844) [INFO] * 2024-07-09 22:13:46 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-09 22:13:46 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-09 22:13:47 (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 22:13:47 (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 22:13:47 (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 22:13:47 (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 22:13:47 (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 22:13:47 (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 22:13: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-09 22:13:49 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-09 22:13:49 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-09 22:13:49 (6814) [INFO] * 2024-07-09 22:13:49 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-09 22:13:49 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-09 22:13:49 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-09 22:13:49 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-09 22:13:49 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-09 22:13:49 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-09 22:13:49 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-09 22:13:49 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-09 22:13:49 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-09 22:13:49 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-09 22:13:49 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-09 22:13:49 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-09 22:13:49 (6844) [INFO] * 2024-07-09 22:13:51 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-09 22:13:51 (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 22:13:51 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-09 22:13:52 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LobokZdhvj/ea_profile.json * 2024-07-09 22:13:53 (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/LobokZdhvj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-09 22:13:53 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-10 22:13:55 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-10 22:13:55 (8071) [INFO] Script is up to date. * 2024-07-10 22:13:56 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-10 22:13:56 (6814) [INFO] * 2024-07-10 22:13:59 (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": 9, "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 22:13:59 (6844) [INFO] * 2024-07-10 22:14:00 (727) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-10 22:14:00 (734) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-10 22:14:03 (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 22:14:03 (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 22:14:03 (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 22:14:03 (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 22:14:03 (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 22:14:03 (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 22:14:05 (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 22:14:05 (2000) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-10 22:14:05 (6813) [INFO] Running: /usr/bin/yum clean all * 2024-07-10 22:14:05 (6814) [INFO] * 2024-07-10 22:14:05 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-10 22:14:06 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-10 22:14:06 (6827) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-10 22:14:06 (6827) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-10 22:14:06 (6827) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-10 22:14:06 (6827) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-10 22:14:06 (6827) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-10 22:14:06 (6827) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-10 22:14:06 (6827) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-10 22:14:06 (6827) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-10 22:14:06 (6827) [INFO] Cleaning up list of fastest mirrors * 2024-07-10 22:14:06 (6827) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-10 22:14:06 (6844) [INFO] * 2024-07-10 22:14:10 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading * 2024-07-10 22:14:10 (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 22:14:10 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-10 22:14:11 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XJhstTtQaI/ea_profile.json * 2024-07-10 22:14:15 (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/XJhstTtQaI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959. * 2024-07-10 22:14:15 (321) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-11 22:13:49 (8049) [INFO] Self-update of script version 45 requested. * 2024-07-11 22:13:49 (8054) [INFO] Newer version of script found. Downloading. * 2024-07-11 22:13:50 (8063) [INFO] Script update to version 47 successful. * 2024-07-11 22:13:51 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-11 22:13:51 (6849) [INFO] * 2024-07-11 22:13:53 (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": 9, "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 22:13:54 (6879) [INFO] * 2024-07-11 22:13:54 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-11 22:13:54 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-11 22:13:54 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-11 22:13:54 (6849) [INFO] * 2024-07-11 22:13:56 (6879) [INFO] * 2024-07-11 22:13: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-11 22:13:59 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-11 22:13:59 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-11 22:13:59 (6849) [INFO] * 2024-07-11 22:13:59 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-11 22:14:00 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-11 22:14:00 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-11 22:14:00 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-11 22:14:00 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-11 22:14:00 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-11 22:14:00 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-11 22:14:00 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-11 22:14:00 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-11 22:14:00 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-11 22:14:00 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-11 22:14:00 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-11 22:14:00 (6879) [INFO] * 2024-07-11 22:14:03 (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 22:14:03 (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 22:14:03 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-11 22:14:04 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RjWBl8HrnM/ea_profile.json * 2024-07-11 22:14:05 (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/RjWBl8HrnM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-11 22:14:05 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-12 22:13:47 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-12 22:13:47 (8150) [INFO] Script is up to date. * 2024-07-12 22:13:48 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-12 22:13:48 (6849) [INFO] * 2024-07-12 22:13:51 (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": 9, "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 22:13:51 (6879) [INFO] * 2024-07-12 22:13:52 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-12 22:13:52 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-12 22:13:52 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-12 22:13:52 (6849) [INFO] * 2024-07-12 22:13:54 (6879) [INFO] * 2024-07-12 22:13: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-12 22:13:57 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-12 22:13:57 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-12 22:13:57 (6849) [INFO] * 2024-07-12 22:13:57 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-12 22:13:58 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-12 22:13:58 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-12 22:13:58 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-12 22:13:58 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-12 22:13:58 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-12 22:13:58 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-12 22:13:58 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-12 22:13:58 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-12 22:13:58 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-12 22:13:58 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-12 22:13:58 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-12 22:13:58 (6879) [INFO] * 2024-07-12 22:14:03 (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 22:14:03 (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 22:14:04 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-12 22:14:04 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1yfXI9IUqw/ea_profile.json * 2024-07-12 22:14: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/1yfXI9IUqw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-12 22:14:06 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-13 22:14:35 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-13 22:14:35 (8150) [INFO] Script is up to date. * 2024-07-13 22:14:36 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-13 22:14:36 (6849) [INFO] * 2024-07-13 22:14:41 (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": 9, "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 22:14:41 (6879) [INFO] * 2024-07-13 22:14:42 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-13 22:14:42 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-13 22:14:42 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-13 22:14:42 (6849) [INFO] * 2024-07-13 22:14:43 (6879) [INFO] * 2024-07-13 22:14:47 (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 22:14:47 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-13 22:14:47 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-13 22:14:47 (6849) [INFO] * 2024-07-13 22:14:47 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-13 22:14:48 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-13 22:14:48 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-13 22:14:48 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-13 22:14:48 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-13 22:14:48 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-13 22:14:48 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-13 22:14:48 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-13 22:14:48 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-13 22:14:48 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-13 22:14:48 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-13 22:14:48 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-13 22:14:48 (6879) [INFO] * 2024-07-13 22:14:51 (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 22:14:51 (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 22:14:51 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-13 22:14:52 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pM5l0uGchH/ea_profile.json * 2024-07-13 22:14: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/pM5l0uGchH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-13 22:14:54 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-14 22:14:36 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-14 22:14:36 (8150) [INFO] Script is up to date. * 2024-07-14 22:14:37 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-14 22:14:37 (6849) [INFO] * 2024-07-14 22:14:40 (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": 9, "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 22:14:40 (6879) [INFO] * 2024-07-14 22:14:40 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-14 22:14:40 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-14 22:14:40 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-14 22:14:40 (6849) [INFO] * 2024-07-14 22:14:42 (6879) [INFO] * 2024-07-14 22:14:45 (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 22:14:45 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-14 22:14:45 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-14 22:14:45 (6849) [INFO] * 2024-07-14 22:14:45 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-14 22:14:46 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-14 22:14:46 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-14 22:14:46 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-14 22:14:46 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-14 22:14:46 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-14 22:14:46 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-14 22:14:46 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-14 22:14:46 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-14 22:14:46 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-14 22:14:46 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-14 22:14:46 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-14 22:14:46 (6879) [INFO] * 2024-07-14 22:14:48 (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 22:14:48 (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 22:14:48 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-14 22:14:49 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z8H918lGrZ/ea_profile.json * 2024-07-14 22:14:50 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z8H918lGrZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-14 22:14:50 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-15 22:13:41 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-15 22:13:42 (8150) [INFO] Script is up to date. * 2024-07-15 22:13:43 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-15 22:13:43 (6849) [INFO] * 2024-07-15 22:13:46 (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": 9, "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 22:13:46 (6879) [INFO] * 2024-07-15 22:13:47 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-15 22:13:47 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-15 22:13:47 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-15 22:13:47 (6849) [INFO] * 2024-07-15 22:13:49 (6879) [INFO] * 2024-07-15 22:13: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-15 22:13:52 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-15 22:13:52 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-15 22:13:52 (6849) [INFO] * 2024-07-15 22:13:52 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-15 22:13:53 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-15 22:13:53 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-15 22:13:53 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-15 22:13:53 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-15 22:13:53 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-15 22:13:53 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-15 22:13:53 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-15 22:13:53 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-15 22:13:53 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-15 22:13:53 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-15 22:13:53 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-15 22:13:53 (6879) [INFO] * 2024-07-15 22:13:56 (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 22:13:56 (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 22:13:56 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-15 22:13:57 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/I88GOkjQqu/ea_profile.json * 2024-07-15 22:13:59 (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/I88GOkjQqu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-15 22:13:59 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-16 22:13:44 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-16 22:13:44 (8150) [INFO] Script is up to date. * 2024-07-16 22:13:45 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-16 22:13:45 (6849) [INFO] * 2024-07-16 22:13:48 (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": 9, "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 22:13:48 (6879) [INFO] * 2024-07-16 22:13:48 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-16 22:13:48 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-16 22:13:49 (6848) [INFO] Running: /usr/bin/yum list extras * 2024-07-16 22:13:49 (6849) [INFO] * 2024-07-16 22:13:50 (6879) [INFO] * 2024-07-16 22:13: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-16 22:13:54 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-16 22:13:54 (6848) [INFO] Running: /usr/bin/yum clean all * 2024-07-16 22:13:54 (6849) [INFO] * 2024-07-16 22:13:54 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-16 22:13:54 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-16 22:13:54 (6862) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-16 22:13:54 (6862) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-16 22:13:54 (6862) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-16 22:13:54 (6862) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-16 22:13:54 (6862) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-16 22:13:54 (6862) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-16 22:13:54 (6862) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-16 22:13:54 (6862) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-16 22:13:54 (6862) [INFO] Cleaning up list of fastest mirrors * 2024-07-16 22:13:54 (6862) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-16 22:13:54 (6879) [INFO] * 2024-07-16 22:13:57 (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 22:13:57 (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 22:13:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-16 22:13:58 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1dUQ8QneEG/ea_profile.json * 2024-07-16 22:14:00 (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/1dUQ8QneEG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992. * 2024-07-16 22:14:00 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-17 22:13:48 (8128) [INFO] Self-update of script version 47 requested. * 2024-07-17 22:13:48 (8133) [INFO] Newer version of script found. Downloading. * 2024-07-17 22:13:48 (8142) [INFO] Script update to version 48 successful. * 2024-07-17 22:13:49 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-17 22:13:49 (6847) [INFO] * 2024-07-17 22:13:52 (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": 9, "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 22:13:52 (6877) [INFO] * 2024-07-17 22:13:53 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-17 22:13:53 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-17 22:13:53 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-17 22:13:53 (6847) [INFO] * 2024-07-17 22:13:55 (6877) [INFO] * 2024-07-17 22:13: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 22:13:59 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-17 22:13:59 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-17 22:13:59 (6847) [INFO] * 2024-07-17 22:13:59 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-17 22:13:59 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-17 22:13:59 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-17 22:13:59 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-17 22:13:59 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-17 22:13:59 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-17 22:13:59 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-17 22:13:59 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-17 22:13:59 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-17 22:13:59 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-17 22:13:59 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-17 22:13:59 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-17 22:13:59 (6877) [INFO] * 2024-07-17 22:14:03 (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 22:14:03 (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 22:14:03 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-17 22:14:04 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0NNdh_y7of/ea_profile.json * 2024-07-17 22:14:05 (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/0NNdh_y7of/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-17 22:14:05 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-18 22:13:37 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-18 22:13:37 (8148) [INFO] Script is up to date. * 2024-07-18 22:13:38 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-18 22:13:38 (6847) [INFO] * 2024-07-18 22:13: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": 9, "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 22:13:41 (6877) [INFO] * 2024-07-18 22:13:41 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-18 22:13:41 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-18 22:13:42 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-18 22:13:42 (6847) [INFO] * 2024-07-18 22:13:43 (6877) [INFO] * 2024-07-18 22:13: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-18 22:13:46 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-18 22:13:46 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-18 22:13:46 (6847) [INFO] * 2024-07-18 22:13:46 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-18 22:13:46 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-18 22:13:46 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-18 22:13:46 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-18 22:13:46 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-18 22:13:46 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-18 22:13:46 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-18 22:13:46 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-18 22:13:46 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-18 22:13:46 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-18 22:13:47 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-18 22:13:47 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-18 22:13:47 (6877) [INFO] * 2024-07-18 22:13: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-18 22:13: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-18 22:13:51 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-18 22:13:51 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rRdh03SgJT/ea_profile.json * 2024-07-18 22:13: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/rRdh03SgJT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-18 22:13:53 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-19 22:13:40 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-19 22:13:40 (8148) [INFO] Script is up to date. * 2024-07-19 22:13:41 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-19 22:13:41 (6847) [INFO] * 2024-07-19 22:13: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": 9, "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 22:13:44 (6877) [INFO] * 2024-07-19 22:13:45 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-19 22:13:45 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-19 22:13:45 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-19 22:13:45 (6847) [INFO] * 2024-07-19 22:13:48 (6877) [INFO] * 2024-07-19 22:13: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-19 22:13:52 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-19 22:13:52 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-19 22:13:52 (6847) [INFO] * 2024-07-19 22:13:52 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-19 22:13:52 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-19 22:13:52 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-19 22:13:52 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-19 22:13:52 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-19 22:13:52 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-19 22:13:52 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-19 22:13:52 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-19 22:13:52 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-19 22:13:52 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-19 22:13:52 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-19 22:13:52 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-19 22:13:52 (6877) [INFO] * 2024-07-19 22:13: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-19 22:13: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-19 22:13:55 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-19 22:13:55 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p3RWf4i1wb/ea_profile.json * 2024-07-19 22:13: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/p3RWf4i1wb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-19 22:13:57 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-20 22:14:36 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-20 22:14:36 (8148) [INFO] Script is up to date. * 2024-07-20 22:14:37 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-20 22:14:37 (6847) [INFO] * 2024-07-20 22:14: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": 9, "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 22:14:41 (6877) [INFO] * 2024-07-20 22:14:42 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-20 22:14:42 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-20 22:14:42 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-20 22:14:42 (6847) [INFO] * 2024-07-20 22:14:44 (6877) [INFO] * 2024-07-20 22:14:49 (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 22:14:49 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-20 22:14:49 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-20 22:14:49 (6847) [INFO] * 2024-07-20 22:14:49 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-20 22:14:49 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-20 22:14:49 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-20 22:14:49 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-20 22:14:49 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-20 22:14:49 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-20 22:14:49 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-20 22:14:49 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-20 22:14:49 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-20 22:14:49 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-20 22:14:49 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-20 22:14:49 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-20 22:14:49 (6877) [INFO] * 2024-07-20 22:14:52 (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 22:14:52 (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 22:14:52 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-20 22:14:53 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mrvUVvQTbk/ea_profile.json * 2024-07-20 22:14:55 (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/mrvUVvQTbk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-20 22:14:55 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-21 22:14:30 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-21 22:14:30 (8148) [INFO] Script is up to date. * 2024-07-21 22:14:31 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-21 22:14:31 (6847) [INFO] * 2024-07-21 22:14: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": 9, "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 22:14:34 (6877) [INFO] * 2024-07-21 22:14:34 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-21 22:14:34 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-21 22:14:34 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-21 22:14:34 (6847) [INFO] * 2024-07-21 22:14:36 (6877) [INFO] * 2024-07-21 22:14:39 (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 22:14:39 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-21 22:14:39 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-21 22:14:39 (6847) [INFO] * 2024-07-21 22:14:39 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-21 22:14:39 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-21 22:14:39 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-21 22:14:39 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-21 22:14:39 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-21 22:14:39 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-21 22:14:39 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-21 22:14:39 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-21 22:14:39 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-21 22:14:39 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-21 22:14:39 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-21 22:14:39 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-21 22:14:39 (6877) [INFO] * 2024-07-21 22:14: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-21 22:14: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-21 22:14:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-21 22:14:43 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DWNSMqSgEP/ea_profile.json * 2024-07-21 22:14: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/DWNSMqSgEP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-21 22:14:44 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-22 22:13:44 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-22 22:13:44 (8148) [INFO] Script is up to date. * 2024-07-22 22:13:45 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-22 22:13:45 (6847) [INFO] * 2024-07-22 22:13:48 (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": 9, "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 22:13:48 (6877) [INFO] * 2024-07-22 22:13:49 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-22 22:13:49 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-22 22:13:49 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-22 22:13:49 (6847) [INFO] * 2024-07-22 22:13:50 (6877) [INFO] * 2024-07-22 22:13: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-22 22:13:54 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-22 22:13:54 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-22 22:13:54 (6847) [INFO] * 2024-07-22 22:13:54 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-22 22:13:54 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-22 22:13:54 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-22 22:13:54 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-22 22:13:54 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-22 22:13:54 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-22 22:13:54 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-22 22:13:54 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-22 22:13:54 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-22 22:13:54 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-22 22:13:55 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-22 22:13:55 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-22 22:13:55 (6877) [INFO] * 2024-07-22 22:14:01 (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 22:14:01 (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 22:14:01 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-22 22:14:02 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gglTEqx3LL/ea_profile.json * 2024-07-22 22:14:03 (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/gglTEqx3LL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-22 22:14:03 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-23 22:13:45 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-23 22:13:45 (8148) [INFO] Script is up to date. * 2024-07-23 22:13:46 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-23 22:13:46 (6847) [INFO] * 2024-07-23 22:13:49 (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": 9, "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 22:13:49 (6877) [INFO] * 2024-07-23 22:13:50 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-23 22:13:50 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-23 22:13:50 (6846) [INFO] Running: /usr/bin/yum list extras * 2024-07-23 22:13:50 (6847) [INFO] * 2024-07-23 22:13:52 (6877) [INFO] * 2024-07-23 22:13: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-23 22:13:56 (2026) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-23 22:13:56 (6846) [INFO] Running: /usr/bin/yum clean all * 2024-07-23 22:13:56 (6847) [INFO] * 2024-07-23 22:13:56 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-23 22:13:56 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-23 22:13:56 (6860) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-23 22:13:56 (6860) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-23 22:13:56 (6860) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-23 22:13:56 (6860) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-23 22:13:56 (6860) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-23 22:13:56 (6860) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-23 22:13:56 (6860) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-23 22:13:56 (6860) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-23 22:13:56 (6860) [INFO] Cleaning up list of fastest mirrors * 2024-07-23 22:13:56 (6860) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-23 22:13:56 (6877) [INFO] * 2024-07-23 22:14:00 (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 22:14:00 (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 22:14:00 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-23 22:14:01 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hX8zPU_CIb/ea_profile.json * 2024-07-23 22:14: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/hX8zPU_CIb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990. * 2024-07-23 22:14:02 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-24 22:13:45 (8126) [INFO] Self-update of script version 48 requested. * 2024-07-24 22:13:45 (8131) [INFO] Newer version of script found. Downloading. * 2024-07-24 22:13:46 (8140) [INFO] Script update to version 49 successful. * 2024-07-24 22:13:47 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-24 22:13:47 (6908) [INFO] * 2024-07-24 22:13:50 (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": 9, "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 22:13:50 (6938) [INFO] * 2024-07-24 22:13:50 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-24 22:13:50 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-24 22:13:50 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-24 22:13:50 (6908) [INFO] * 2024-07-24 22:13:52 (6938) [INFO] * 2024-07-24 22:13:56 (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 22:13:56 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-24 22:13:56 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-24 22:13:56 (6908) [INFO] * 2024-07-24 22:13:56 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-24 22:13:57 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-24 22:13:57 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-24 22:13:57 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-24 22:13:57 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-24 22:13:57 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-24 22:13:57 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-24 22:13:57 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-24 22:13:57 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-24 22:13:57 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-24 22:13:57 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-24 22:13:57 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-24 22:13:57 (6938) [INFO] * 2024-07-24 22:13:59 (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 22:13:59 (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 22:14:00 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-24 22:14:01 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K4Fgk8ZyUR/ea_profile.json * 2024-07-24 22:14: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/K4Fgk8ZyUR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-24 22:14:02 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-25 22:13:42 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-25 22:13:42 (8209) [INFO] Script is up to date. * 2024-07-25 22:13:43 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-25 22:13:43 (6908) [INFO] * 2024-07-25 22:13:47 (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": 9, "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 22:13:47 (6938) [INFO] * 2024-07-25 22:13:48 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-25 22:13:48 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-25 22:13:48 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-25 22:13:48 (6908) [INFO] * 2024-07-25 22:13:50 (6938) [INFO] * 2024-07-25 22:13: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-25 22:13:54 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-25 22:13:54 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-25 22:13:54 (6908) [INFO] * 2024-07-25 22:13:54 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-25 22:13:54 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-25 22:13:54 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-25 22:13:54 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-25 22:13:54 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-25 22:13:54 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-25 22:13:54 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-25 22:13:54 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-25 22:13:54 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-25 22:13:54 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-25 22:13:54 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-25 22:13:54 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-25 22:13:54 (6938) [INFO] * 2024-07-25 22:13:56 (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 22:13:56 (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 22:13:57 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-25 22:13:57 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ndH8y_w72v/ea_profile.json * 2024-07-25 22:13:59 (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/ndH8y_w72v/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-25 22:13:59 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-26 22:13:42 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-26 22:13:42 (8209) [INFO] Script is up to date. * 2024-07-26 22:13:43 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-26 22:13:43 (6908) [INFO] * 2024-07-26 22:13:46 (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": 9, "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 22:13:46 (6938) [INFO] * 2024-07-26 22:13:46 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-26 22:13:46 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-26 22:13:46 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-26 22:13:46 (6908) [INFO] * 2024-07-26 22:13:48 (6938) [INFO] * 2024-07-26 22:13:51 (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 22:13:51 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-26 22:13:51 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-26 22:13:51 (6908) [INFO] * 2024-07-26 22:13:52 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-26 22:13:52 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-26 22:13:52 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-26 22:13:52 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-26 22:13:52 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-26 22:13:52 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-26 22:13:52 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-26 22:13:52 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-26 22:13:52 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-26 22:13:52 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-26 22:13:52 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-26 22:13:52 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-26 22:13:52 (6938) [INFO] * 2024-07-26 22:13:55 (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 22:13:55 (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 22:13:56 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-26 22:13:57 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Q7QXRGsdiZ/ea_profile.json * 2024-07-26 22:13: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/Q7QXRGsdiZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-26 22:13:58 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-27 22:14:29 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-27 22:14:29 (8209) [INFO] Script is up to date. * 2024-07-27 22:14:30 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-27 22:14:30 (6908) [INFO] * 2024-07-27 22:14: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": 9, "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 22:14:33 (6938) [INFO] * 2024-07-27 22:14:34 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-27 22:14:34 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-27 22:14:34 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-27 22:14:34 (6908) [INFO] * 2024-07-27 22:14:35 (6938) [INFO] * 2024-07-27 22:14:38 (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 22:14:38 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-27 22:14:38 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-27 22:14:38 (6908) [INFO] * 2024-07-27 22:14:39 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-27 22:14:39 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-27 22:14:39 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-27 22:14:39 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-27 22:14:39 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-27 22:14:39 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-27 22:14:39 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-27 22:14:39 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-27 22:14:39 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-27 22:14:39 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-27 22:14:39 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-27 22:14:39 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-27 22:14:39 (6938) [INFO] * 2024-07-27 22:14:42 (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 22:14:42 (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 22:14:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-27 22:14:43 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LJMgVLMD4e/ea_profile.json * 2024-07-27 22:14: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/LJMgVLMD4e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-27 22:14:44 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-28 22:14:28 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-28 22:14:28 (8209) [INFO] Script is up to date. * 2024-07-28 22:14:29 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-28 22:14:29 (6908) [INFO] * 2024-07-28 22:14:32 (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": 9, "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 22:14:32 (6938) [INFO] * 2024-07-28 22:14:32 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-28 22:14:32 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-28 22:14:32 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-28 22:14:32 (6908) [INFO] * 2024-07-28 22:14:34 (6938) [INFO] * 2024-07-28 22:14:38 (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 22:14:38 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-28 22:14:38 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-28 22:14:38 (6908) [INFO] * 2024-07-28 22:14:38 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-28 22:14:38 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-28 22:14:38 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-28 22:14:38 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-28 22:14:38 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-28 22:14:38 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-28 22:14:38 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-28 22:14:38 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-28 22:14:38 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-28 22:14:38 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-28 22:14:38 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-28 22:14:38 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-28 22:14:39 (6938) [INFO] * 2024-07-28 22:14:43 (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 22:14:43 (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 22:14:43 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-28 22:14:44 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_SLaR7C4xh/ea_profile.json * 2024-07-28 22:14:46 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_SLaR7C4xh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-28 22:14:46 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-29 22:13:40 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-29 22:13:40 (8209) [INFO] Script is up to date. * 2024-07-29 22:13:41 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-29 22:13:41 (6908) [INFO] * 2024-07-29 22:13:43 (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": 9, "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 22:13:43 (6938) [INFO] * 2024-07-29 22:13:43 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-29 22:13:43 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-29 22:13:43 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-29 22:13:43 (6908) [INFO] * 2024-07-29 22:13:45 (6938) [INFO] * 2024-07-29 22:13: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-29 22:13:48 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-29 22:13:48 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-29 22:13:48 (6908) [INFO] * 2024-07-29 22:13:48 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-29 22:13:48 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-29 22:13:48 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-29 22:13:48 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-29 22:13:48 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-29 22:13:48 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-29 22:13:48 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-29 22:13:48 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-29 22:13:48 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-29 22:13:48 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-29 22:13:48 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-29 22:13:48 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-29 22:13:48 (6938) [INFO] * 2024-07-29 22:13: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-29 22:13: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-29 22:13:52 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-29 22:13:53 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/k4Oktl1ouk/ea_profile.json * 2024-07-29 22:13: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/k4Oktl1ouk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-29 22:13:54 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-30 22:13:38 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-30 22:13:38 (8209) [INFO] Script is up to date. * 2024-07-30 22:13:39 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-30 22:13:39 (6908) [INFO] * 2024-07-30 22:13:43 (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": 9, "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 22:13:43 (6938) [INFO] * 2024-07-30 22:13:43 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-30 22:13:43 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-30 22:13:43 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-30 22:13:43 (6908) [INFO] * 2024-07-30 22:13:45 (6938) [INFO] * 2024-07-30 22:13:49 (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 22:13:49 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-30 22:13:49 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-30 22:13:49 (6908) [INFO] * 2024-07-30 22:13:49 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-30 22:13:49 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-30 22:13:49 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-30 22:13:49 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-30 22:13:49 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-30 22:13:49 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-30 22:13:49 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-30 22:13:49 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-30 22:13:49 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-30 22:13:49 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-30 22:13:50 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-30 22:13:50 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-30 22:13:50 (6938) [INFO] * 2024-07-30 22:13: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 22:13: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 22:13:53 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-30 22:13:54 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0PeDozwRJC/ea_profile.json * 2024-07-30 22:13: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/0PeDozwRJC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-30 22:13:56 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-07-31 22:13:46 (8187) [INFO] Self-update of script version 49 requested. * 2024-07-31 22:13:47 (8209) [INFO] Script is up to date. * 2024-07-31 22:13:47 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-07-31 22:13:47 (6908) [INFO] * 2024-07-31 22:13:51 (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": 9, "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 22:13:51 (6938) [INFO] * 2024-07-31 22:13:52 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-07-31 22:13:52 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-07-31 22:13:52 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-07-31 22:13:52 (6908) [INFO] * 2024-07-31 22:13:54 (6938) [INFO] * 2024-07-31 22:13:58 (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 22:13:58 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-07-31 22:13:58 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-07-31 22:13:58 (6908) [INFO] * 2024-07-31 22:13:58 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-07-31 22:13:58 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-07-31 22:13:58 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-07-31 22:13:58 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-07-31 22:13:58 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-07-31 22:13:58 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-07-31 22:13:58 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-07-31 22:13:58 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-07-31 22:13:58 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-07-31 22:13:58 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-07-31 22:13:58 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-07-31 22:13:58 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-07-31 22:13:58 (6938) [INFO] * 2024-07-31 22:14: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-31 22:14: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-31 22:14:01 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-07-31 22:14:02 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/906UR8o562/ea_profile.json * 2024-07-31 22:14:03 (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/906UR8o562/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-07-31 22:14:03 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-01 22:13:42 (8187) [INFO] Self-update of script version 49 requested. * 2024-08-01 22:13:42 (8209) [INFO] Script is up to date. * 2024-08-01 22:13:43 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-01 22:13:43 (6908) [INFO] * 2024-08-01 22:13:46 (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": 9, "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 22:13:46 (6938) [INFO] * 2024-08-01 22:13:47 (744) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-01 22:13:47 (751) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-01 22:13:47 (6907) [INFO] Running: /usr/bin/yum list extras * 2024-08-01 22:13:47 (6908) [INFO] * 2024-08-01 22:13:48 (6938) [INFO] * 2024-08-01 22:13:55 (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 22:13:55 (2048) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-01 22:13:55 (6907) [INFO] Running: /usr/bin/yum clean all * 2024-08-01 22:13:55 (6908) [INFO] * 2024-08-01 22:13:55 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-01 22:13:55 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-01 22:13:55 (6921) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-01 22:13:55 (6921) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-01 22:13:55 (6921) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-01 22:13:55 (6921) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-01 22:13:55 (6921) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-01 22:13:55 (6921) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-01 22:13:55 (6921) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-01 22:13:55 (6921) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-01 22:13:55 (6921) [INFO] Cleaning up list of fastest mirrors * 2024-08-01 22:13:55 (6921) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-01 22:13:55 (6938) [INFO] * 2024-08-01 22:13:57 (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 22:13:57 (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 22:13:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-01 22:13:59 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lEalcZ5yYM/ea_profile.json * 2024-08-01 22:14:00 (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/lEalcZ5yYM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051. * 2024-08-01 22:14:00 (338) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-02 22:13:39 (8187) [INFO] Self-update of script version 49 requested. * 2024-08-02 22:13:40 (8192) [INFO] Newer version of script found. Downloading. * 2024-08-02 22:13:41 (8201) [INFO] Script update to version 50 successful. * 2024-08-02 22:13:42 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-02 22:13:42 (7164) [INFO] * 2024-08-02 22:13:47 (756) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-02 22:13:47 (763) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-02 22:13:47 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-02 22:13:47 (7164) [INFO] * 2024-08-02 22:13:55 (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 22:13:55 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-02 22:13:55 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-02 22:13:55 (7164) [INFO] * 2024-08-02 22:13:55 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-02 22:13:55 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-02 22:13:55 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-02 22:13:55 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-02 22:13:55 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-02 22:13:55 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-02 22:13:55 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-02 22:13:55 (7177) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-02 22:13:55 (7177) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-02 22:13:55 (7177) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-02 22:13:55 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-02 22:13:55 (7177) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-02 22:13:55 (7194) [INFO] * 2024-08-02 22:13: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 22:13: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 22:13:58 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-02 22:13:59 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/37RxbMDte3/ea_profile.json * 2024-08-02 22:14: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/37RxbMDte3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307. * 2024-08-02 22:14:01 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-03 22:14:34 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-03 22:14:34 (8496) [INFO] Script is up to date. * 2024-08-03 22:14:35 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-03 22:14:35 (7164) [INFO] * 2024-08-03 22:14:39 (756) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-03 22:14:39 (763) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-03 22:14:39 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-03 22:14:39 (7164) [INFO] * 2024-08-03 22:14:46 (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 22:14:46 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-03 22:14:46 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-03 22:14:46 (7164) [INFO] * 2024-08-03 22:14:46 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-03 22:14:46 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-03 22:14:46 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-03 22:14:46 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-03 22:14:46 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-03 22:14:46 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-03 22:14:46 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-03 22:14:46 (7177) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-03 22:14:46 (7177) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-03 22:14:46 (7177) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-03 22:14:46 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-03 22:14:46 (7177) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-03 22:14:46 (7194) [INFO] * 2024-08-03 22:14:48 (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 22:14:48 (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 22:14:48 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-03 22:14:49 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FQlK34CFhI/ea_profile.json * 2024-08-03 22:14: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/FQlK34CFhI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307. * 2024-08-03 22:14:51 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-04 22:14:29 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-04 22:14:29 (8496) [INFO] Script is up to date. * 2024-08-04 22:14:30 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-04 22:14:30 (7164) [INFO] * 2024-08-04 22:14:34 (756) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-04 22:14:34 (763) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-04 22:14:34 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-04 22:14:34 (7164) [INFO] * 2024-08-04 22:14:38 (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 22:14:38 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-04 22:14:38 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-04 22:14:38 (7164) [INFO] * 2024-08-04 22:14:38 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-04 22:14:39 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-04 22:14:39 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-04 22:14:39 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-04 22:14:39 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-04 22:14:39 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-04 22:14:39 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-04 22:14:39 (7177) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-04 22:14:39 (7177) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-04 22:14:39 (7177) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-04 22:14:39 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-04 22:14:39 (7177) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-04 22:14:39 (7194) [INFO] * 2024-08-04 22:14:41 (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 22:14:41 (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 22:14:41 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-04 22:14:42 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TY0DbEooxp/ea_profile.json * 2024-08-04 22:14:43 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TY0DbEooxp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307. * 2024-08-04 22:14:43 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-05 22:13:38 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-05 22:13:38 (8496) [INFO] Script is up to date. * 2024-08-05 22:13:39 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-05 22:13:39 (7164) [INFO] * 2024-08-05 22:13:44 (756) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-05 22:13:44 (763) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-05 22:13:44 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-05 22:13:44 (7164) [INFO] * 2024-08-05 22:13:49 (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 22:13:49 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-05 22:13:49 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-05 22:13:49 (7164) [INFO] * 2024-08-05 22:13:49 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-05 22:13:49 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-05 22:13:49 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-05 22:13:49 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-05 22:13:49 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-05 22:13:49 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-05 22:13:49 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-05 22:13:49 (7177) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-05 22:13:49 (7177) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-05 22:13:49 (7177) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-05 22:13:49 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-05 22:13:49 (7177) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-05 22:13:49 (7194) [INFO] * 2024-08-05 22:13:51 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-08-05 22:13:51 (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 22:13:52 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-05 22:13:53 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GNVwQckcLR/ea_profile.json * 2024-08-05 22:13: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/GNVwQckcLR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307. * 2024-08-05 22:13:54 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-06 22:13:45 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-06 22:13:45 (8496) [INFO] Script is up to date. * 2024-08-06 22:13:46 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-06 22:13:46 (7164) [INFO] * 2024-08-06 22:13:54 (756) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-06 22:13:54 (763) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-06 22:13:54 (7163) [INFO] Running: /usr/bin/yum list extras * 2024-08-06 22:13:54 (7164) [INFO] * 2024-08-06 22:14:00 (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 22:14:00 (2060) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-06 22:14:00 (7163) [INFO] Running: /usr/bin/yum clean all * 2024-08-06 22:14:00 (7164) [INFO] * 2024-08-06 22:14:00 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-06 22:14:01 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-06 22:14:01 (7177) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-06 22:14:01 (7177) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-06 22:14:01 (7177) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-06 22:14:01 (7177) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-06 22:14:01 (7177) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-06 22:14:01 (7177) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-06 22:14:01 (7177) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-06 22:14:01 (7177) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-06 22:14:01 (7177) [INFO] Cleaning up list of fastest mirrors * 2024-08-06 22:14:01 (7177) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-06 22:14:01 (7194) [INFO] * 2024-08-06 22:14:03 (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 22:14:03 (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 22:14:03 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-06 22:14:04 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fvfr6wNWsR/ea_profile.json * 2024-08-06 22:14:05 (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/fvfr6wNWsR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307. * 2024-08-06 22:14:05 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-07 22:14:31 (8474) [INFO] Self-update of script version 50 requested. * 2024-08-07 22:14:31 (8479) [INFO] Newer version of script found. Downloading. * 2024-08-07 22:14:32 (8488) [INFO] Script update to version 51 successful. * 2024-08-07 22:14:34 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-07 22:14:34 (7324) [INFO] * 2024-08-07 22:14:38 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-07 22:14:38 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-07 22:14:38 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-07 22:14:38 (7324) [INFO] * 2024-08-07 22:14: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-07 22:14:44 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-07 22:14:44 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-07 22:14:44 (7324) [INFO] * 2024-08-07 22:14:44 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-07 22:14:44 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-07 22:14:44 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-07 22:14:44 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-07 22:14:44 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-07 22:14:44 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-07 22:14:44 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-07 22:14:44 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-07 22:14:44 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-07 22:14:44 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-07 22:14:44 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-07 22:14:44 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-07 22:14:44 (7354) [INFO] * 2024-08-07 22:14: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-07 22:14: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-07 22:14:46 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-07 22:14:47 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4FBCU7HZvK/ea_profile.json * 2024-08-07 22:14:48 (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/4FBCU7HZvK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-07 22:14:48 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-08 22:13:41 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-08 22:13:41 (8664) [INFO] Script is up to date. * 2024-08-08 22:13:42 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-08 22:13:42 (7324) [INFO] * 2024-08-08 22:13:46 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-08 22:13:46 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-08 22:13:46 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-08 22:13:46 (7324) [INFO] * 2024-08-08 22:13: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-08 22:13:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-08 22:13:51 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-08 22:13:51 (7324) [INFO] * 2024-08-08 22:13:51 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-08 22:13:52 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-08 22:13:52 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-08 22:13:52 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-08 22:13:52 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-08 22:13:52 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-08 22:13:52 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-08 22:13:52 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-08 22:13:52 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-08 22:13:52 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-08 22:13:52 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-08 22:13:52 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-08 22:13:52 (7354) [INFO] * 2024-08-08 22:13:54 (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 22:13:54 (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 22:13:55 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-08 22:13:56 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/M7OdZ6naUe/ea_profile.json * 2024-08-08 22:13: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/M7OdZ6naUe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-08 22:13:57 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-09 22:13:44 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-09 22:13:44 (8664) [INFO] Script is up to date. * 2024-08-09 22:13:45 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-09 22:13:45 (7324) [INFO] * 2024-08-09 22:13:49 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-09 22:13:49 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-09 22:13:49 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-09 22:13:49 (7324) [INFO] * 2024-08-09 22:13:56 (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 22:13:56 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-09 22:13:56 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-09 22:13:56 (7324) [INFO] * 2024-08-09 22:13:56 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-09 22:13:56 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-09 22:13:56 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-09 22:13:56 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-09 22:13:56 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-09 22:13:56 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-09 22:13:56 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-09 22:13:56 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-09 22:13:56 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-09 22:13:56 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-09 22:13:56 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-09 22:13:56 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-09 22:13:56 (7354) [INFO] * 2024-08-09 22:13: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-09 22:13: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-09 22:13:59 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-09 22:14:00 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/culCMJqlNv/ea_profile.json * 2024-08-09 22:14: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/culCMJqlNv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-09 22:14:02 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-10 22:14:37 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-10 22:14:37 (8664) [INFO] Script is up to date. * 2024-08-10 22:14:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-10 22:14:39 (7324) [INFO] * 2024-08-10 22:14:45 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-10 22:14:45 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-10 22:14:45 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-10 22:14:45 (7324) [INFO] * 2024-08-10 22:14: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-10 22:14:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-10 22:14:51 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-10 22:14:51 (7324) [INFO] * 2024-08-10 22:14:51 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-10 22:14:52 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-10 22:14:52 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-10 22:14:52 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-10 22:14:52 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-10 22:14:52 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-10 22:14:52 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-10 22:14:52 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-10 22:14:52 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-10 22:14:52 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-10 22:14:52 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-10 22:14:52 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-10 22:14:52 (7354) [INFO] * 2024-08-10 22:14:54 (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 22:14:54 (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 22:14:55 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-10 22:14:56 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5HOgRpLIuK/ea_profile.json * 2024-08-10 22:14: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/5HOgRpLIuK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-10 22:14:57 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-11 22:14:30 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-11 22:14:30 (8664) [INFO] Script is up to date. * 2024-08-11 22:14:31 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-11 22:14:31 (7324) [INFO] * 2024-08-11 22:14:35 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-11 22:14:35 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-11 22:14:35 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-11 22:14:35 (7324) [INFO] * 2024-08-11 22:14: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-11 22:14:41 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-11 22:14:41 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-11 22:14:41 (7324) [INFO] * 2024-08-11 22:14:41 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-11 22:14:41 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-11 22:14:41 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-11 22:14:41 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-11 22:14:41 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-11 22:14:41 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-11 22:14:41 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-11 22:14:41 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-11 22:14:41 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-11 22:14:41 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-11 22:14:41 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-11 22:14:41 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-11 22:14:41 (7354) [INFO] * 2024-08-11 22:14:44 (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 22:14:44 (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 22:14:44 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-11 22:14:45 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WI4Gi5uyKI/ea_profile.json * 2024-08-11 22:14: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/WI4Gi5uyKI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-11 22:14:47 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-12 22:13:41 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-12 22:13:41 (8664) [INFO] Script is up to date. * 2024-08-12 22:13:42 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-12 22:13:42 (7324) [INFO] * 2024-08-12 22:13:46 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-12 22:13:46 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-12 22:13:46 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-12 22:13:46 (7324) [INFO] * 2024-08-12 22:13: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 22:13:53 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-12 22:13:53 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-12 22:13:53 (7324) [INFO] * 2024-08-12 22:13:53 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-12 22:13:54 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-12 22:13:54 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-12 22:13:54 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-12 22:13:54 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-12 22:13:54 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-12 22:13:54 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-12 22:13:54 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-12 22:13:54 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-12 22:13:54 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-12 22:13:54 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-12 22:13:54 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-12 22:13:54 (7354) [INFO] * 2024-08-12 22:13:56 (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 22:13:56 (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 22:13:56 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-12 22:13:57 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BusyS_KaXk/ea_profile.json * 2024-08-12 22:13: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/BusyS_KaXk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-12 22:13:58 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-13 22:13:42 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-13 22:13:42 (8664) [INFO] Script is up to date. * 2024-08-13 22:13:43 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-13 22:13:43 (7324) [INFO] * 2024-08-13 22:13:46 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-13 22:13:46 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-13 22:13:46 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-13 22:13:46 (7324) [INFO] * 2024-08-13 22:13:52 (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 22:13:52 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-13 22:13:52 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-13 22:13:52 (7324) [INFO] * 2024-08-13 22:13:52 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-13 22:13:53 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-13 22:13:53 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-13 22:13:53 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-13 22:13:53 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-13 22:13:53 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-13 22:13:53 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-13 22:13:53 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-13 22:13:53 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-13 22:13:53 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-13 22:13:53 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-13 22:13:53 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-13 22:13:53 (7354) [INFO] * 2024-08-13 22:13: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-13 22:13: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-13 22:13:55 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-13 22:13:56 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b4uRlnTONL/ea_profile.json * 2024-08-13 22:13: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/b4uRlnTONL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-13 22:13:57 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-14 22:13:43 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-14 22:13:43 (8664) [INFO] Script is up to date. * 2024-08-14 22:13:44 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-14 22:13:44 (7324) [INFO] * 2024-08-14 22:13:49 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-14 22:13:49 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-14 22:13:49 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-14 22:13:49 (7324) [INFO] * 2024-08-14 22:13: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-14 22:13:54 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-14 22:13:54 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-14 22:13:54 (7324) [INFO] * 2024-08-14 22:13:55 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-14 22:13:55 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-14 22:13:55 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-14 22:13:55 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-14 22:13:55 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-14 22:13:55 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-14 22:13:55 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-14 22:13:55 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-14 22:13:55 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-14 22:13:55 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-14 22:13:55 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-14 22:13:55 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-14 22:13:55 (7354) [INFO] * 2024-08-14 22:13:58 (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 22:13:58 (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-14 22:13:58 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-14 22:13:59 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ltRHpbh8MY/ea_profile.json * 2024-08-14 22:14: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/ltRHpbh8MY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-14 22:14:00 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-15 22:14:36 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-15 22:14:36 (8664) [INFO] Script is up to date. * 2024-08-15 22:14:37 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-15 22:14:37 (7324) [INFO] * 2024-08-15 22:14:43 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-15 22:14:43 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-15 22:14:43 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-15 22:14:43 (7324) [INFO] * 2024-08-15 22:14: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-15 22:14:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-15 22:14:51 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-15 22:14:51 (7324) [INFO] * 2024-08-15 22:14:51 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-15 22:14:51 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-15 22:14:51 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-15 22:14:51 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-15 22:14:51 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-15 22:14:51 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-15 22:14:51 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-15 22:14:51 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-15 22:14:51 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-15 22:14:51 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-15 22:14:51 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-15 22:14:51 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-15 22:14:51 (7354) [INFO] * 2024-08-15 22:14: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-15 22:14: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-15 22:14:54 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-15 22:14:55 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CJNBdvNbuc/ea_profile.json * 2024-08-15 22:14: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/CJNBdvNbuc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-15 22:14:57 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-16 22:13:44 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-16 22:13:44 (8664) [INFO] Script is up to date. * 2024-08-16 22:13:45 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-16 22:13:45 (7324) [INFO] * 2024-08-16 22:13:50 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-16 22:13:50 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-16 22:13:50 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-16 22:13:50 (7324) [INFO] * 2024-08-16 22:13:56 (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 22:13:56 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-16 22:13:56 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-16 22:13:56 (7324) [INFO] * 2024-08-16 22:13:56 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-16 22:13:57 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-16 22:13:57 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-16 22:13:57 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-16 22:13:57 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-16 22:13:57 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-16 22:13:57 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-16 22:13:57 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-16 22:13:57 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-16 22:13:57 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-16 22:13:57 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-16 22:13:57 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-16 22:13:57 (7354) [INFO] * 2024-08-16 22:13: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-16 22:13: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-16 22:13:59 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-16 22:14:00 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nbjR0ofRiA/ea_profile.json * 2024-08-16 22:14:03 (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/nbjR0ofRiA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-16 22:14:03 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-17 22:14:35 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-17 22:14:35 (8664) [INFO] Script is up to date. * 2024-08-17 22:14:37 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-17 22:14:37 (7324) [INFO] * 2024-08-17 22:14:40 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-17 22:14:40 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-17 22:14:40 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-17 22:14:40 (7324) [INFO] * 2024-08-17 22:14: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-17 22:14:46 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-17 22:14:46 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-17 22:14:46 (7324) [INFO] * 2024-08-17 22:14:46 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-17 22:14:47 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-17 22:14:47 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-17 22:14:47 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-17 22:14:47 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-17 22:14:47 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-17 22:14:47 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-17 22:14:47 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-17 22:14:47 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-17 22:14:47 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-17 22:14:47 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-17 22:14:47 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-17 22:14:47 (7354) [INFO] * 2024-08-17 22:14:50 (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 22:14:50 (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 22:14:50 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-17 22:14:51 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/W0_Z42soSe/ea_profile.json * 2024-08-17 22:14: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/W0_Z42soSe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-17 22:14:53 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-18 22:14:32 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-18 22:14:32 (8664) [INFO] Script is up to date. * 2024-08-18 22:14:33 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-18 22:14:33 (7324) [INFO] * 2024-08-18 22:14:36 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-18 22:14:36 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-18 22:14:36 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-18 22:14:36 (7324) [INFO] * 2024-08-18 22:14:43 (2029) [WARN] Initial run of "yum makecache" failed: http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found 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. One of the configured repositories failed (CentOS-7 - Base), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=base ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable base or subscription-manager repos --disable=base 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=base.skip_if_unavailable=true failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to 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 22:14:43 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-18 22:14:43 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-18 22:14:43 (7324) [INFO] * 2024-08-18 22:14:44 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-18 22:14:44 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-18 22:14:44 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-18 22:14:44 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-18 22:14:44 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-18 22:14:44 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-18 22:14:44 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-18 22:14:44 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-18 22:14:44 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-18 22:14:44 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-18 22:14:44 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-18 22:14:44 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-18 22:14:44 (7354) [INFO] * 2024-08-18 22:14: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 22:14:47 (2040) [ERROR] http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below 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://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found 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. One of the configured repositories failed (CentOS-7 - Base), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=base ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable base or subscription-manager repos --disable=base 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=base.skip_if_unavailable=true failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to 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 22:14:48 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-18 22:14:48 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bZHxoy7TZn/ea_profile.json * 2024-08-18 22:14: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/bZHxoy7TZn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-18 22:14:51 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-19 22:13:44 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-19 22:13:44 (8664) [INFO] Script is up to date. * 2024-08-19 22:13:46 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-19 22:13:46 (7324) [INFO] * 2024-08-19 22:13:51 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-19 22:13:51 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-19 22:13:51 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-19 22:13:51 (7324) [INFO] * 2024-08-19 22:13:57 (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 22:13:57 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-19 22:13:57 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-19 22:13:57 (7324) [INFO] * 2024-08-19 22:13:57 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-19 22:13:58 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-19 22:13:58 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-19 22:13:58 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-19 22:13:58 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-19 22:13:58 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-19 22:13:58 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-19 22:13:58 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-19 22:13:58 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-19 22:13:58 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-19 22:13:58 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-19 22:13:58 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-19 22:13:58 (7354) [INFO] * 2024-08-19 22:14:01 (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 22:14:01 (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 22:14:01 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-19 22:14:02 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pa6OdEygqr/ea_profile.json * 2024-08-19 22:14: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/pa6OdEygqr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-19 22:14:04 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-20 22:13:47 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-20 22:13:48 (8664) [INFO] Script is up to date. * 2024-08-20 22:13:49 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-20 22:13:49 (7324) [INFO] * 2024-08-20 22:13:54 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-20 22:13:54 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-20 22:13:54 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-20 22:13:54 (7324) [INFO] * 2024-08-20 22:14:00 (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 22:14:00 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-20 22:14:00 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-20 22:14:00 (7324) [INFO] * 2024-08-20 22:14:00 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-20 22:14:00 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-20 22:14:00 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-20 22:14:00 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-20 22:14:00 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-20 22:14:00 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-20 22:14:00 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-20 22:14:00 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-20 22:14:00 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-20 22:14:00 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-20 22:14:00 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-20 22:14:00 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-20 22:14:00 (7354) [INFO] * 2024-08-20 22:14:03 (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 22:14:03 (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 22:14:03 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-20 22:14:04 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HSiMMeqRfy/ea_profile.json * 2024-08-20 22:14:05 (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/HSiMMeqRfy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-20 22:14:05 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-21 22:13:49 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-21 22:13:49 (8664) [INFO] Script is up to date. * 2024-08-21 22:13:50 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-21 22:13:50 (7324) [INFO] * 2024-08-21 22:13:55 (739) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-21 22:13:55 (746) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-21 22:13:55 (7323) [INFO] Running: /usr/bin/yum list extras * 2024-08-21 22:13:55 (7324) [INFO] * 2024-08-21 22:14:01 (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 22:14:01 (2030) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-21 22:14:01 (7323) [INFO] Running: /usr/bin/yum clean all * 2024-08-21 22:14:01 (7324) [INFO] * 2024-08-21 22:14:01 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-21 22:14:02 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-21 22:14:02 (7337) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-21 22:14:02 (7337) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-21 22:14:02 (7337) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-21 22:14:02 (7337) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-21 22:14:02 (7337) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-21 22:14:02 (7337) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-21 22:14:02 (7337) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-21 22:14:02 (7337) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-21 22:14:02 (7337) [INFO] Cleaning up list of fastest mirrors * 2024-08-21 22:14:02 (7337) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-21 22:14:02 (7354) [INFO] * 2024-08-21 22:14:04 (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 22:14:04 (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 22:14:04 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-21 22:14:05 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TxA1htzdEL/ea_profile.json * 2024-08-21 22:14:06 (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/TxA1htzdEL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444. * 2024-08-21 22:14:06 (350) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-22 22:13:45 (8642) [INFO] Self-update of script version 51 requested. * 2024-08-22 22:13:45 (8647) [INFO] Newer version of script found. Downloading. * 2024-08-22 22:13:45 (8656) [INFO] Script update to version 52 successful. * 2024-08-22 22:13:47 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-22 22:13:47 (7574) [INFO] * 2024-08-22 22:13:52 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-22 22:13:52 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-22 22:13:52 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-22 22:13:52 (7574) [INFO] * 2024-08-22 22:14:03 (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 22:14:03 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-22 22:14:03 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-22 22:14:03 (7574) [INFO] * 2024-08-22 22:14:03 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-22 22:14:03 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-22 22:14:03 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-22 22:14:03 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-22 22:14:03 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-22 22:14:03 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-22 22:14:03 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-22 22:14:03 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-22 22:14:03 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-22 22:14:03 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-22 22:14:03 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-22 22:14:03 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-22 22:14:03 (7604) [INFO] * 2024-08-22 22:14:05 (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 22:14:05 (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 22:14:06 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-22 22:14:07 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tTeMwackqV/ea_profile.json * 2024-08-22 22:14: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/tTeMwackqV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-22 22:14:08 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-23 22:13:45 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-23 22:13:45 (8939) [INFO] Script is up to date. * 2024-08-23 22:13:47 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-23 22:13:47 (7574) [INFO] * 2024-08-23 22:13:50 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-23 22:13:50 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-23 22:13:50 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-23 22:13:50 (7574) [INFO] * 2024-08-23 22:13: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-23 22:13:55 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-23 22:13:55 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-23 22:13:55 (7574) [INFO] * 2024-08-23 22:13:56 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-23 22:13:56 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-23 22:13:56 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-23 22:13:56 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-23 22:13:56 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-23 22:13:56 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-23 22:13:56 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-23 22:13:56 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-23 22:13:56 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-23 22:13:56 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-23 22:13:56 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-23 22:13:56 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-23 22:13:56 (7604) [INFO] * 2024-08-23 22:13:59 (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 22:13:59 (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 22:14:00 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-23 22:14:00 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TJRN_CkYBg/ea_profile.json * 2024-08-23 22:14: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/TJRN_CkYBg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-23 22:14:02 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-24 22:14:32 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-24 22:14:33 (8939) [INFO] Script is up to date. * 2024-08-24 22:14:34 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-24 22:14:34 (7574) [INFO] * 2024-08-24 22:14:37 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-24 22:14:37 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-24 22:14:37 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-24 22:14:37 (7574) [INFO] * 2024-08-24 22:14:42 (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 22:14:42 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-24 22:14:42 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-24 22:14:42 (7574) [INFO] * 2024-08-24 22:14:42 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-24 22:14:42 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-24 22:14:42 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-24 22:14:42 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-24 22:14:42 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-24 22:14:42 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-24 22:14:42 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-24 22:14:42 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-24 22:14:42 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-24 22:14:42 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-24 22:14:42 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-24 22:14:42 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-24 22:14:42 (7604) [INFO] * 2024-08-24 22:14:45 (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 22:14:45 (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 22:14:46 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-24 22:14:46 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ijvNt_Mp7s/ea_profile.json * 2024-08-24 22:14:47 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ijvNt_Mp7s/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-24 22:14:47 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-25 22:14:31 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-25 22:14:31 (8939) [INFO] Script is up to date. * 2024-08-25 22:14:32 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-25 22:14:32 (7574) [INFO] * 2024-08-25 22:14:36 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-25 22:14:36 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-25 22:14:36 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-25 22:14:36 (7574) [INFO] * 2024-08-25 22:14: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-25 22:14:44 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-25 22:14:44 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-25 22:14:44 (7574) [INFO] * 2024-08-25 22:14:44 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-25 22:14:44 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-25 22:14:44 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-25 22:14:44 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-25 22:14:44 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-25 22:14:44 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-25 22:14:44 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-25 22:14:44 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-25 22:14:44 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-25 22:14:44 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-25 22:14:44 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-25 22:14:44 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-25 22:14:44 (7604) [INFO] * 2024-08-25 22:14:47 (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 22:14:47 (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 22:14:47 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-25 22:14:48 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nUnPAQ10ET/ea_profile.json * 2024-08-25 22:14: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/nUnPAQ10ET/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-25 22:14:50 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-26 22:13:48 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-26 22:13:49 (8939) [INFO] Script is up to date. * 2024-08-26 22:13:50 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-26 22:13:50 (7574) [INFO] * 2024-08-26 22:13:54 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-26 22:13:54 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-26 22:13:54 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-26 22:13:54 (7574) [INFO] * 2024-08-26 22:14:03 (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 22:14:03 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-26 22:14:03 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-26 22:14:03 (7574) [INFO] * 2024-08-26 22:14:03 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-26 22:14:03 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-26 22:14:03 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-26 22:14:03 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-26 22:14:03 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-26 22:14:03 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-26 22:14:03 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-26 22:14:03 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-26 22:14:03 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-26 22:14:03 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-26 22:14:03 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-26 22:14:03 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-26 22:14:03 (7604) [INFO] * 2024-08-26 22:14:06 (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 22:14:06 (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 22:14:06 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-26 22:14:07 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ipBdT1uQ1B/ea_profile.json * 2024-08-26 22:14: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/ipBdT1uQ1B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-26 22:14:08 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-27 22:13:42 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-27 22:13:42 (8939) [INFO] Script is up to date. * 2024-08-27 22:13:43 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-27 22:13:43 (7574) [INFO] * 2024-08-27 22:13:46 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-27 22:13:46 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-27 22:13:46 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-27 22:13:46 (7574) [INFO] * 2024-08-27 22:13: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-27 22:13:53 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-27 22:13:53 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-27 22:13:53 (7574) [INFO] * 2024-08-27 22:13:53 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-27 22:13:53 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-27 22:13:53 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-27 22:13:53 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-27 22:13:53 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-27 22:13:53 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-27 22:13:53 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-27 22:13:53 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-27 22:13:53 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-27 22:13:53 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-27 22:13:53 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-27 22:13:53 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-27 22:13:53 (7604) [INFO] * 2024-08-27 22:13:57 (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 22:13:57 (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 22:13:57 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-27 22:13:58 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z507uzD5Ym/ea_profile.json * 2024-08-27 22:13: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/Z507uzD5Ym/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-27 22:13:59 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-28 22:13:43 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-28 22:13:43 (8939) [INFO] Script is up to date. * 2024-08-28 22:13:44 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-28 22:13:44 (7574) [INFO] * 2024-08-28 22:13:47 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-28 22:13:47 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-28 22:13:47 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-28 22:13:47 (7574) [INFO] * 2024-08-28 22:13: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 22:13:53 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-28 22:13:53 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-28 22:13:53 (7574) [INFO] * 2024-08-28 22:13:53 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-28 22:13:53 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-28 22:13:53 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-28 22:13:53 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-28 22:13:53 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-28 22:13:53 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-28 22:13:53 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-28 22:13:53 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-28 22:13:53 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-28 22:13:53 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-28 22:13:53 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-28 22:13:53 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-28 22:13:53 (7604) [INFO] * 2024-08-28 22:13:56 (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 22:13:56 (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 22:13:57 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-28 22:13:57 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Agc7XVlBVH/ea_profile.json * 2024-08-28 22:13: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/Agc7XVlBVH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-28 22:13:59 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-29 22:13:38 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-29 22:13:38 (8939) [INFO] Script is up to date. * 2024-08-29 22:13:39 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-29 22:13:39 (7574) [INFO] * 2024-08-29 22:13:42 (673) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-29 22:13:42 (680) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-29 22:13:42 (7573) [INFO] Running: /usr/bin/yum list extras * 2024-08-29 22:13:42 (7574) [INFO] * 2024-08-29 22:13:47 (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 22:13:47 (1964) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-29 22:13:47 (7573) [INFO] Running: /usr/bin/yum clean all * 2024-08-29 22:13:47 (7574) [INFO] * 2024-08-29 22:13:47 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-29 22:13:48 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-29 22:13:48 (7587) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-29 22:13:48 (7587) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-29 22:13:48 (7587) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-29 22:13:48 (7587) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-29 22:13:48 (7587) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-29 22:13:48 (7587) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-29 22:13:48 (7587) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-29 22:13:48 (7587) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-29 22:13:48 (7587) [INFO] Cleaning up list of fastest mirrors * 2024-08-29 22:13:48 (7587) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-29 22:13:48 (7604) [INFO] * 2024-08-29 22:13:51 (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 22:13:51 (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 22:13:52 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-29 22:13:53 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RLN55aruPZ/ea_profile.json * 2024-08-29 22:13: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/RLN55aruPZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694. * 2024-08-29 22:13:54 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-30 22:13:44 (8917) [INFO] Self-update of script version 52 requested. * 2024-08-30 22:13:44 (8922) [INFO] Newer version of script found. Downloading. * 2024-08-30 22:13:44 (8931) [INFO] Script update to version 53 successful. * 2024-08-30 22:13:45 (231) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-08-30 22:13:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-30 22:13:46 (7647) [INFO] * 2024-08-30 22:13:49 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-30 22:13:49 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-30 22:13:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-08-30 22:13:49 (7647) [INFO] * 2024-08-30 22:13:55 (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 22:13:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-30 22:13:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-08-30 22:13:55 (7647) [INFO] * 2024-08-30 22:13:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-30 22:13:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-30 22:13:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-30 22:13:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-30 22:13:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-30 22:13:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-30 22:13:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-30 22:13:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-30 22:13:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-30 22:13:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-30 22:13:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-08-30 22:13:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-30 22:13:55 (7677) [INFO] * 2024-08-30 22:13: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-08-30 22:13: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-08-30 22:13:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-30 22:14:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dIm8akaL3a/ea_profile.json * 2024-08-30 22:14: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/dIm8akaL3a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-08-30 22:14:01 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-08-31 22:14:44 (8992) [INFO] Self-update of script version 53 requested. * 2024-08-31 22:14:44 (9014) [INFO] Script is up to date. * 2024-08-31 22:14:45 (231) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-08-31 22:14:45 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-08-31 22:14:45 (7647) [INFO] * 2024-08-31 22:14:49 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-08-31 22:14:49 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-08-31 22:14:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-08-31 22:14:49 (7647) [INFO] * 2024-08-31 22:14:55 (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 22:14:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-08-31 22:14:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-08-31 22:14:55 (7647) [INFO] * 2024-08-31 22:14:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-08-31 22:14:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-08-31 22:14:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-08-31 22:14:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-08-31 22:14:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-08-31 22:14:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-08-31 22:14:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-08-31 22:14:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-08-31 22:14:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-08-31 22:14:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-08-31 22:14:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-08-31 22:14:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-08-31 22:14:55 (7677) [INFO] * 2024-08-31 22:14: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-08-31 22:14: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-08-31 22:15:00 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-08-31 22:15:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OFUZbbQY_Y/ea_profile.json * 2024-08-31 22:15: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/OFUZbbQY_Y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-08-31 22:15:03 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-01 22:14:34 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-01 22:14:34 (9014) [INFO] Script is up to date. * 2024-09-01 22:14:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-01 22:14:36 (7647) [INFO] * 2024-09-01 22:14:39 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-01 22:14:39 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-01 22:14:39 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-01 22:14:39 (7647) [INFO] * 2024-09-01 22:14:45 (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 22:14:45 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-01 22:14:45 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-01 22:14:45 (7647) [INFO] * 2024-09-01 22:14:45 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-01 22:14:45 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-01 22:14:45 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-01 22:14:45 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-01 22:14:45 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-01 22:14:45 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-01 22:14:45 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-01 22:14:45 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-01 22:14:45 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-01 22:14:45 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-01 22:14:45 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-01 22:14:45 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-01 22:14:45 (7677) [INFO] * 2024-09-01 22:14:48 (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 22:14:48 (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 22:14:49 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-01 22:14:49 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9KGy9UToZf/ea_profile.json * 2024-09-01 22:14: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/9KGy9UToZf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-01 22:14:51 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-02 22:13:44 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-02 22:13:44 (9014) [INFO] Script is up to date. * 2024-09-02 22:13:45 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-02 22:13:45 (7647) [INFO] * 2024-09-02 22:13:48 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-02 22:13:48 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-02 22:13:48 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-02 22:13:48 (7647) [INFO] * 2024-09-02 22:13:53 (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 22:13:53 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-02 22:13:53 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-02 22:13:53 (7647) [INFO] * 2024-09-02 22:13:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-02 22:13:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-02 22:13:54 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-02 22:13:54 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-02 22:13:54 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-02 22:13:54 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-02 22:13:54 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-02 22:13:54 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-02 22:13:54 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-02 22:13:54 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-02 22:13:54 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-02 22:13:54 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-02 22:13:54 (7677) [INFO] * 2024-09-02 22:13: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-02 22:13: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-02 22:13:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-02 22:13:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MGekzafv7z/ea_profile.json * 2024-09-02 22:14: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/MGekzafv7z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-02 22:14:01 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-03 22:13:50 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-03 22:13:50 (9014) [INFO] Script is up to date. * 2024-09-03 22:13:51 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-03 22:13:51 (7647) [INFO] * 2024-09-03 22:13:54 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-03 22:13:54 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-03 22:13:54 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-03 22:13:54 (7647) [INFO] * 2024-09-03 22:14:00 (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 22:14:00 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-03 22:14:00 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-03 22:14:00 (7647) [INFO] * 2024-09-03 22:14:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-03 22:14:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-03 22:14:00 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-03 22:14:00 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-03 22:14:00 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-03 22:14:00 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-03 22:14:00 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-03 22:14:00 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-03 22:14:00 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-03 22:14:00 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-03 22:14:00 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-03 22:14:00 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-03 22:14:00 (7677) [INFO] * 2024-09-03 22:14: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-03 22:14: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-03 22:14:04 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-03 22:14:04 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tWi_bTl507/ea_profile.json * 2024-09-03 22:14:07 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tWi_bTl507/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-03 22:14:07 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-04 22:13:42 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-04 22:13:42 (9014) [INFO] Script is up to date. * 2024-09-04 22:13:43 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-04 22:13:43 (7647) [INFO] * 2024-09-04 22:13:49 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-04 22:13:49 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-04 22:13:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-04 22:13:49 (7647) [INFO] * 2024-09-04 22:13:55 (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 22:13:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-04 22:13:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-04 22:13:55 (7647) [INFO] * 2024-09-04 22:13:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-04 22:13:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-04 22:13:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-04 22:13:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-04 22:13:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-04 22:13:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-04 22:13:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-04 22:13:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-04 22:13:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-04 22:13:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-04 22:13:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-04 22:13:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-04 22:13:55 (7677) [INFO] * 2024-09-04 22:13: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-04 22:13: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-04 22:13:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-04 22:14:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7Qrki5MIU9/ea_profile.json * 2024-09-04 22:14: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/7Qrki5MIU9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-04 22:14:01 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-05 22:13:45 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-05 22:13:45 (9014) [INFO] Script is up to date. * 2024-09-05 22:13:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-05 22:13:46 (7647) [INFO] * 2024-09-05 22:13:52 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-05 22:13:52 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-05 22:13:52 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-05 22:13:52 (7647) [INFO] * 2024-09-05 22:14:02 (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 22:14:02 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-05 22:14:02 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-05 22:14:02 (7647) [INFO] * 2024-09-05 22:14:02 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-05 22:14:03 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-05 22:14:03 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-05 22:14:03 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-05 22:14:03 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-05 22:14:03 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-05 22:14:03 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-05 22:14:03 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-05 22:14:03 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-05 22:14:03 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-05 22:14:03 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-05 22:14:03 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-05 22:14:03 (7677) [INFO] * 2024-09-05 22:14:05 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-05 22:14:05 (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 22:14:05 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-05 22:14:06 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WQD9kXyMUk/ea_profile.json * 2024-09-05 22:14:08 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WQD9kXyMUk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-05 22:14:08 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-06 22:13:40 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-06 22:13:40 (9014) [INFO] Script is up to date. * 2024-09-06 22:13:41 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-06 22:13:41 (7647) [INFO] * 2024-09-06 22:13:45 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-06 22:13:45 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-06 22:13:45 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-06 22:13:45 (7647) [INFO] * 2024-09-06 22:13:55 (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 22:13:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-06 22:13:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-06 22:13:55 (7647) [INFO] * 2024-09-06 22:13:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-06 22:13:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-06 22:13:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-06 22:13:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-06 22:13:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-06 22:13:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-06 22:13:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-06 22:13:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-06 22:13:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-06 22:13:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-06 22:13:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-06 22:13:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-06 22:13:55 (7677) [INFO] * 2024-09-06 22:13: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-06 22:13: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-06 22:13:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-06 22:14:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RQ8jK3WI3Z/ea_profile.json * 2024-09-06 22:14: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/RQ8jK3WI3Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-06 22:14:01 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-07 22:14:36 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-07 22:14:36 (9014) [INFO] Script is up to date. * 2024-09-07 22:14:37 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-07 22:14:37 (7647) [INFO] * 2024-09-07 22:14:41 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-07 22:14:41 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-07 22:14:41 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-07 22:14:41 (7647) [INFO] * 2024-09-07 22:14: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-07 22:14:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-07 22:14:48 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-07 22:14:48 (7647) [INFO] * 2024-09-07 22:14:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-07 22:14:49 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-07 22:14:49 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-07 22:14:49 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-07 22:14:49 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-07 22:14:49 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-07 22:14:49 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-07 22:14:49 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-07 22:14:49 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-07 22:14:49 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-07 22:14:49 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-07 22:14:49 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-07 22:14:49 (7677) [INFO] * 2024-09-07 22:14: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-07 22:14: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-07 22:14:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-07 22:14:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X814BEOHMD/ea_profile.json * 2024-09-07 22:14: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/X814BEOHMD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-07 22:14:56 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-08 22:14:43 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-08 22:14:43 (9014) [INFO] Script is up to date. * 2024-09-08 22:14:44 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-08 22:14:44 (7647) [INFO] * 2024-09-08 22:14:48 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-08 22:14:48 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-08 22:14:48 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-08 22:14:48 (7647) [INFO] * 2024-09-08 22:14:53 (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 22:14:53 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-08 22:14:53 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-08 22:14:53 (7647) [INFO] * 2024-09-08 22:14:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-08 22:14:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-08 22:14:54 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-08 22:14:54 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-08 22:14:54 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-08 22:14:54 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-08 22:14:54 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-08 22:14:54 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-08 22:14:54 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-08 22:14:54 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-08 22:14:54 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-08 22:14:54 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-08 22:14:54 (7677) [INFO] * 2024-09-08 22:14: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-08 22:14: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-08 22:14:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-08 22:14:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QicBNm6aIJ/ea_profile.json * 2024-09-08 22:14: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/QicBNm6aIJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-08 22:14:58 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-09 22:13:39 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-09 22:13:39 (9014) [INFO] Script is up to date. * 2024-09-09 22:13:40 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-09 22:13:40 (7647) [INFO] * 2024-09-09 22:13:43 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-09 22:13:43 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-09 22:13:43 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-09 22:13:43 (7647) [INFO] * 2024-09-09 22:13: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-09 22:13:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-09 22:13:48 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-09 22:13:48 (7647) [INFO] * 2024-09-09 22:13:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-09 22:13:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-09 22:13:48 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-09 22:13:48 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-09 22:13:48 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-09 22:13:48 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-09 22:13:48 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-09 22:13:48 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-09 22:13:48 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-09 22:13:48 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-09 22:13:48 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-09 22:13:48 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-09 22:13:48 (7677) [INFO] * 2024-09-09 22:13: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-09 22:13: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-09 22:13:51 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-09 22:13:52 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LrF4tFFuDD/ea_profile.json * 2024-09-09 22:13: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/LrF4tFFuDD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-09 22:13:53 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-10 22:13:45 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-10 22:13:45 (9014) [INFO] Script is up to date. * 2024-09-10 22:13:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-10 22:13:46 (7647) [INFO] * 2024-09-10 22:13:50 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-10 22:13:50 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-10 22:13:50 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-10 22:13:50 (7647) [INFO] * 2024-09-10 22:13:55 (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 22:13:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-10 22:13:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-10 22:13:55 (7647) [INFO] * 2024-09-10 22:13:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-10 22:13:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-10 22:13:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-10 22:13:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-10 22:13:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-10 22:13:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-10 22:13:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-10 22:13:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-10 22:13:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-10 22:13:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-10 22:13:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-10 22:13:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-10 22:13:55 (7677) [INFO] * 2024-09-10 22:13:57 (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 22:13:57 (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 22:13:57 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-10 22:13:58 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cX3GKQphCD/ea_profile.json * 2024-09-10 22:13: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/cX3GKQphCD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-10 22:14:00 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-11 22:13:44 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-11 22:13:44 (9014) [INFO] Script is up to date. * 2024-09-11 22:13:45 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-11 22:13:45 (7647) [INFO] * 2024-09-11 22:13:49 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-11 22:13:49 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-11 22:13:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-11 22:13:49 (7647) [INFO] * 2024-09-11 22:13: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-11 22:13:57 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-11 22:13:57 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-11 22:13:57 (7647) [INFO] * 2024-09-11 22:13:57 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-11 22:13:57 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-11 22:13:57 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-11 22:13:57 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-11 22:13:57 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-11 22:13:57 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-11 22:13:57 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-11 22:13:57 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-11 22:13:57 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-11 22:13:57 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-11 22:13:57 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-11 22:13:57 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-11 22:13:57 (7677) [INFO] * 2024-09-11 22:14:00 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-11 22:14:00 (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 22:14:00 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-11 22:14:01 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5f0lIGDTDE/ea_profile.json * 2024-09-11 22:14: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/5f0lIGDTDE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-11 22:14:03 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-12 22:13:44 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-12 22:13:45 (9014) [INFO] Script is up to date. * 2024-09-12 22:13:46 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-12 22:13:46 (7647) [INFO] * 2024-09-12 22:13:50 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-12 22:13:50 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-12 22:13:50 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-12 22:13:50 (7647) [INFO] * 2024-09-12 22:13: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-12 22:13:56 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-12 22:13:56 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-12 22:13:56 (7647) [INFO] * 2024-09-12 22:13:56 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-12 22:13:56 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-12 22:13:56 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-12 22:13:56 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-12 22:13:56 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-12 22:13:56 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-12 22:13:56 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-12 22:13:56 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-12 22:13:56 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-12 22:13:56 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-12 22:13:56 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-12 22:13:56 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-12 22:13:56 (7677) [INFO] * 2024-09-12 22:13: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-12 22:13: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-12 22:13:59 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-12 22:14:00 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rhuD40jLTZ/ea_profile.json * 2024-09-12 22:14: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/rhuD40jLTZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-12 22:14:02 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-13 22:13:46 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-13 22:13:46 (9014) [INFO] Script is up to date. * 2024-09-13 22:13:47 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-13 22:13:47 (7647) [INFO] * 2024-09-13 22:13:52 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-13 22:13:52 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-13 22:13:52 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-13 22:13:52 (7647) [INFO] * 2024-09-13 22:14:01 (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 22:14:01 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-13 22:14:01 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-13 22:14:01 (7647) [INFO] * 2024-09-13 22:14:01 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-13 22:14:01 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-13 22:14:01 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-13 22:14:01 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-13 22:14:01 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-13 22:14:01 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-13 22:14:01 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-13 22:14:01 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-13 22:14:01 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-13 22:14:01 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-13 22:14:01 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-13 22:14:01 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-13 22:14:01 (7677) [INFO] * 2024-09-13 22:14:04 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-13 22:14:04 (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 22:14:04 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-13 22:14:05 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aZVEpeklbt/ea_profile.json * 2024-09-13 22:14:08 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aZVEpeklbt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-13 22:14:08 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-14 22:14:43 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-14 22:14:44 (9014) [INFO] Script is up to date. * 2024-09-14 22:14:45 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-14 22:14:45 (7647) [INFO] * 2024-09-14 22:14:49 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-14 22:14:49 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-14 22:14:49 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-14 22:14:49 (7647) [INFO] * 2024-09-14 22:14:55 (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 22:14:55 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-14 22:14:55 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-14 22:14:55 (7647) [INFO] * 2024-09-14 22:14:55 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-14 22:14:55 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-14 22:14:55 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-14 22:14:55 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-14 22:14:55 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-14 22:14:55 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-14 22:14:55 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-14 22:14:55 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-14 22:14:55 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-14 22:14:55 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-14 22:14:55 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-14 22:14:55 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-14 22:14:55 (7677) [INFO] * 2024-09-14 22:14: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-14 22:14: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-14 22:14:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-14 22:14:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/usfBdmfzMx/ea_profile.json * 2024-09-14 22:15: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/usfBdmfzMx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-14 22:15:01 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-15 22:14:37 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-15 22:14:37 (9014) [INFO] Script is up to date. * 2024-09-15 22:14:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-15 22:14:38 (7647) [INFO] * 2024-09-15 22:14:41 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-15 22:14:41 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-15 22:14:41 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-15 22:14:41 (7647) [INFO] * 2024-09-15 22:14: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-15 22:14:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-15 22:14:48 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-15 22:14:48 (7647) [INFO] * 2024-09-15 22:14:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-15 22:14:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-15 22:14:48 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-15 22:14:48 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-15 22:14:48 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-15 22:14:48 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-15 22:14:48 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-15 22:14:48 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-15 22:14:48 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-15 22:14:48 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-15 22:14:48 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-15 22:14:48 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-15 22:14:48 (7677) [INFO] * 2024-09-15 22:14: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-15 22:14: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-15 22:14:52 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-15 22:14:53 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7aR3FwhCEK/ea_profile.json * 2024-09-15 22:14:55 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7aR3FwhCEK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-15 22:14:55 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-16 22:13:43 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-16 22:13:43 (9014) [INFO] Script is up to date. * 2024-09-16 22:13:44 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-16 22:13:44 (7647) [INFO] * 2024-09-16 22:13:48 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-16 22:13:48 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-16 22:13:48 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-16 22:13:48 (7647) [INFO] * 2024-09-16 22:13:53 (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 22:13:53 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-16 22:13:53 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-16 22:13:53 (7647) [INFO] * 2024-09-16 22:13:53 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-16 22:13:53 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-16 22:13:53 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-16 22:13:53 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-16 22:13:53 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-16 22:13:53 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-16 22:13:53 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-16 22:13:53 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-16 22:13:53 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-16 22:13:53 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-16 22:13:53 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-16 22:13:53 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-16 22:13:53 (7677) [INFO] * 2024-09-16 22:13: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-16 22:13: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-16 22:13:57 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-16 22:13:58 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7gba8o6145/ea_profile.json * 2024-09-16 22:13: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/7gba8o6145/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-16 22:13:59 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-17 22:13:55 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-17 22:13:55 (9014) [INFO] Script is up to date. * 2024-09-17 22:13:56 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-17 22:13:56 (7647) [INFO] * 2024-09-17 22:13:59 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-17 22:13:59 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-17 22:13:59 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-17 22:13:59 (7647) [INFO] * 2024-09-17 22:14:04 (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 22:14:04 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-17 22:14:04 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-17 22:14:04 (7647) [INFO] * 2024-09-17 22:14:05 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-17 22:14:05 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-17 22:14:05 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-17 22:14:05 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-17 22:14:05 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-17 22:14:05 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-17 22:14:05 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-17 22:14:05 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-17 22:14:05 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-17 22:14:05 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-17 22:14:05 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-17 22:14:05 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-17 22:14:05 (7677) [INFO] * 2024-09-17 22:14:08 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-17 22:14:08 (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 22:14:08 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-17 22:14:09 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kHBUwwDpdk/ea_profile.json * 2024-09-17 22:14:11 (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/kHBUwwDpdk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-17 22:14:11 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-18 22:15:20 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-18 22:15:20 (9014) [INFO] Script is up to date. * 2024-09-18 22:15:22 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-18 22:15:22 (7647) [INFO] * 2024-09-18 22:15:27 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-18 22:15:27 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-18 22:15:27 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-18 22:15:27 (7647) [INFO] * 2024-09-18 22:15: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-18 22:15:35 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-18 22:15:35 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-18 22:15:35 (7647) [INFO] * 2024-09-18 22:15:35 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-18 22:15:35 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-18 22:15:35 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-18 22:15:35 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-18 22:15:35 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-18 22:15:35 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-18 22:15:35 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-18 22:15:35 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-18 22:15:35 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-18 22:15:35 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-18 22:15:35 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-18 22:15:35 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-18 22:15:35 (7677) [INFO] * 2024-09-18 22:15:39 (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 22:15:39 (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 22:15:39 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-18 22:15:40 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UOrrIg7eJo/ea_profile.json * 2024-09-18 22:15: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/UOrrIg7eJo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-18 22:15:41 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-19 22:13:46 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-19 22:13:46 (9014) [INFO] Script is up to date. * 2024-09-19 22:13:48 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-19 22:13:48 (7647) [INFO] * 2024-09-19 22:13:52 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-19 22:13:52 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-19 22:13:52 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-19 22:13:52 (7647) [INFO] * 2024-09-19 22:14:00 (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 22:14:00 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-19 22:14:00 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-19 22:14:00 (7647) [INFO] * 2024-09-19 22:14:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-19 22:14:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-19 22:14:00 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-19 22:14:00 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-19 22:14:00 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-19 22:14:00 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-19 22:14:00 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-19 22:14:00 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-19 22:14:00 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-19 22:14:00 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-19 22:14:00 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-19 22:14:00 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-19 22:14:00 (7677) [INFO] * 2024-09-19 22:14: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-19 22:14: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-19 22:14:03 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-19 22:14:04 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/938rYFVa8q/ea_profile.json * 2024-09-19 22:14:06 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/938rYFVa8q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-19 22:14:06 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-20 22:13:50 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-20 22:13:50 (9014) [INFO] Script is up to date. * 2024-09-20 22:13:51 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-20 22:13:51 (7647) [INFO] * 2024-09-20 22:13:55 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-20 22:13:55 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-20 22:13:55 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-20 22:13:55 (7647) [INFO] * 2024-09-20 22:14:01 (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 22:14:01 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-20 22:14:01 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-20 22:14:01 (7647) [INFO] * 2024-09-20 22:14:02 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-20 22:14:02 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-20 22:14:02 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-20 22:14:02 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-20 22:14:02 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-20 22:14:02 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-20 22:14:02 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-20 22:14:02 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-20 22:14:02 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-20 22:14:02 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-20 22:14:02 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-20 22:14:02 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-20 22:14:02 (7677) [INFO] * 2024-09-20 22:14:05 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-20 22:14:05 (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 22:14:05 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-20 22:14:06 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4rT429tdQR/ea_profile.json * 2024-09-20 22:14:08 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4rT429tdQR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-20 22:14:08 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-21 22:15:05 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-21 22:15:06 (9014) [INFO] Script is up to date. * 2024-09-21 22:15:08 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-21 22:15:08 (7647) [INFO] * 2024-09-21 22:15:12 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-21 22:15:12 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-21 22:15:12 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-21 22:15:12 (7647) [INFO] * 2024-09-21 22:15:19 (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 22:15:19 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-21 22:15:19 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-21 22:15:19 (7647) [INFO] * 2024-09-21 22:15:19 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-21 22:15:20 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-21 22:15:20 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-21 22:15:20 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-21 22:15:20 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-21 22:15:20 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-21 22:15:20 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-21 22:15:20 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-21 22:15:20 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-21 22:15:20 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-21 22:15:20 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-21 22:15:20 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-21 22:15:20 (7677) [INFO] * 2024-09-21 22:15:25 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-09-21 22:15:25 (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 22:15:25 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-21 22:15:26 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0tukCA0ZKL/ea_profile.json * 2024-09-21 22:15:31 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0tukCA0ZKL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-21 22:15:31 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-22 22:14:36 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-22 22:14:36 (9014) [INFO] Script is up to date. * 2024-09-22 22:14:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-22 22:14:38 (7647) [INFO] * 2024-09-22 22:14:42 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-22 22:14:42 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-22 22:14:42 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-22 22:14:42 (7647) [INFO] * 2024-09-22 22:14: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-22 22:14:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-22 22:14:49 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-22 22:14:49 (7647) [INFO] * 2024-09-22 22:14:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-22 22:14:50 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-22 22:14:50 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-22 22:14:50 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-22 22:14:50 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-22 22:14:50 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-22 22:14:50 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-22 22:14:50 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-22 22:14:50 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-22 22:14:50 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-22 22:14:50 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-22 22:14:50 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-22 22:14:50 (7677) [INFO] * 2024-09-22 22:14: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-22 22:14: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-22 22:14:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-22 22:14:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p_MIodi9IX/ea_profile.json * 2024-09-22 22:14: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/p_MIodi9IX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-22 22:14:56 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-23 22:13:42 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-23 22:13:43 (9014) [INFO] Script is up to date. * 2024-09-23 22:13:44 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-23 22:13:44 (7647) [INFO] * 2024-09-23 22:13:47 (676) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-23 22:13:47 (683) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-23 22:13:47 (7646) [INFO] Running: /usr/bin/yum list extras * 2024-09-23 22:13:47 (7647) [INFO] * 2024-09-23 22:13: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-23 22:13:56 (1967) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-23 22:13:56 (7646) [INFO] Running: /usr/bin/yum clean all * 2024-09-23 22:13:56 (7647) [INFO] * 2024-09-23 22:13:56 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-23 22:13:56 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-23 22:13:56 (7660) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-23 22:13:56 (7660) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-23 22:13:56 (7660) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-23 22:13:56 (7660) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-23 22:13:56 (7660) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-23 22:13:56 (7660) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-23 22:13:56 (7660) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-23 22:13:56 (7660) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-23 22:13:56 (7660) [INFO] Cleaning up list of fastest mirrors * 2024-09-23 22:13:56 (7660) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-23 22:13:56 (7677) [INFO] * 2024-09-23 22:13: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-23 22:13: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-23 22:13:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-23 22:13:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KVN0CwxTsI/ea_profile.json * 2024-09-23 22:14:00 (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/KVN0CwxTsI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767. * 2024-09-23 22:14:00 (355) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-24 22:13:48 (8992) [INFO] Self-update of script version 53 requested. * 2024-09-24 22:13:49 (8997) [INFO] Newer version of script found. Downloading. * 2024-09-24 22:13:49 (9006) [INFO] Script update to version 54 successful. * 2024-09-24 22:13:51 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-24 22:13:51 (7667) [INFO] * 2024-09-24 22:13:54 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-24 22:13:54 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-24 22:13:54 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-24 22:13:54 (7667) [INFO] * 2024-09-24 22:13:59 (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 22:13:59 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-24 22:13:59 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-24 22:13:59 (7667) [INFO] * 2024-09-24 22:13:59 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-24 22:13:59 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-24 22:13:59 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-24 22:13:59 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-24 22:13:59 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-24 22:13:59 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-24 22:13:59 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-24 22:13:59 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-24 22:13:59 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-24 22:13:59 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-24 22:13:59 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-24 22:13:59 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-24 22:14:00 (7697) [INFO] * 2024-09-24 22:14:01 (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 22:14:01 (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 22:14:02 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-24 22:14:03 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mtf5Pi3htT/ea_profile.json * 2024-09-24 22:14: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/mtf5Pi3htT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-24 22:14:04 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-25 22:13:45 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-25 22:13:45 (9030) [INFO] Script is up to date. * 2024-09-25 22:13:47 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-25 22:13:47 (7667) [INFO] * 2024-09-25 22:13:50 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-25 22:13:50 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-25 22:13:50 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-25 22:13:50 (7667) [INFO] * 2024-09-25 22:13: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-09-25 22:13:58 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-25 22:13:58 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-25 22:13:58 (7667) [INFO] * 2024-09-25 22:13:58 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-25 22:13:58 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-25 22:13:58 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-25 22:13:58 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-25 22:13:58 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-25 22:13:58 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-25 22:13:58 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-25 22:13:58 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-25 22:13:58 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-25 22:13:58 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-25 22:13:58 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-25 22:13:58 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-25 22:13:58 (7697) [INFO] * 2024-09-25 22:14:01 (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 22:14:01 (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 22:14:02 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-25 22:14:03 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vMV8yoNKbW/ea_profile.json * 2024-09-25 22:14: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/vMV8yoNKbW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-25 22:14:05 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-26 22:13:41 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-26 22:13:41 (9030) [INFO] Script is up to date. * 2024-09-26 22:13:43 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-26 22:13:43 (7667) [INFO] * 2024-09-26 22:13:46 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-26 22:13:46 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-26 22:13:46 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-26 22:13:46 (7667) [INFO] * 2024-09-26 22:13:52 (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 22:13:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-26 22:13:52 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-26 22:13:52 (7667) [INFO] * 2024-09-26 22:13:52 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-26 22:13:52 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-26 22:13:52 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-26 22:13:52 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-26 22:13:52 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-26 22:13:52 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-26 22:13:52 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-26 22:13:52 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-26 22:13:52 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-26 22:13:52 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-26 22:13:53 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-26 22:13:53 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-26 22:13:53 (7697) [INFO] * 2024-09-26 22:13: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 22:13: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 22:13:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-26 22:13:58 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SbH4ErGjes/ea_profile.json * 2024-09-26 22:13: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/SbH4ErGjes/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-26 22:13:59 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-27 22:13:47 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-27 22:13:47 (9030) [INFO] Script is up to date. * 2024-09-27 22:13:48 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-27 22:13:48 (7667) [INFO] * 2024-09-27 22:13:54 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-27 22:13:54 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-27 22:13:54 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-27 22:13:54 (7667) [INFO] * 2024-09-27 22:14:01 (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 22:14:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-27 22:14:01 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-27 22:14:01 (7667) [INFO] * 2024-09-27 22:14:01 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-27 22:14:01 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-27 22:14:01 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-27 22:14:01 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-27 22:14:01 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-27 22:14:01 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-27 22:14:01 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-27 22:14:01 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-27 22:14:01 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-27 22:14:01 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-27 22:14:01 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-27 22:14:01 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-27 22:14:01 (7697) [INFO] * 2024-09-27 22:14:03 (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 22:14:03 (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 22:14:04 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-27 22:14:05 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DeBQOtwdFn/ea_profile.json * 2024-09-27 22:14:06 (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/DeBQOtwdFn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-27 22:14:06 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-28 22:14:34 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-28 22:14:34 (9030) [INFO] Script is up to date. * 2024-09-28 22:14:35 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-28 22:14:35 (7667) [INFO] * 2024-09-28 22:14:39 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-28 22:14:39 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-28 22:14:39 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-28 22:14:39 (7667) [INFO] * 2024-09-28 22:14: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-09-28 22:14:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-28 22:14:45 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-28 22:14:45 (7667) [INFO] * 2024-09-28 22:14:45 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-28 22:14:45 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-28 22:14:45 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-28 22:14:45 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-28 22:14:45 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-28 22:14:45 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-28 22:14:45 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-28 22:14:45 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-28 22:14:45 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-28 22:14:45 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-28 22:14:45 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-28 22:14:45 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-28 22:14:45 (7697) [INFO] * 2024-09-28 22:14: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-09-28 22:14: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-09-28 22:14:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-28 22:14:49 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FimQbLXFxG/ea_profile.json * 2024-09-28 22:14: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/FimQbLXFxG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-28 22:14:50 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-29 22:14:33 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-29 22:14:34 (9030) [INFO] Script is up to date. * 2024-09-29 22:14:35 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-29 22:14:35 (7667) [INFO] * 2024-09-29 22:14:38 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-29 22:14:38 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-29 22:14:38 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-29 22:14:38 (7667) [INFO] * 2024-09-29 22:14: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-29 22:14:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-29 22:14:42 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-29 22:14:42 (7667) [INFO] * 2024-09-29 22:14:42 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-29 22:14:42 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-29 22:14:42 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-29 22:14:42 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-29 22:14:42 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-29 22:14:42 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-29 22:14:42 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-29 22:14:42 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-29 22:14:42 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-29 22:14:42 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-29 22:14:42 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-29 22:14:42 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-29 22:14:42 (7697) [INFO] * 2024-09-29 22:14:44 (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 22:14:44 (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 22:14:44 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-29 22:14:45 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5HGAN_FwEd/ea_profile.json * 2024-09-29 22:14:46 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5HGAN_FwEd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-29 22:14:46 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-09-30 22:13:41 (9008) [INFO] Self-update of script version 54 requested. * 2024-09-30 22:13:42 (9030) [INFO] Script is up to date. * 2024-09-30 22:13:43 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-09-30 22:13:43 (7667) [INFO] * 2024-09-30 22:13:48 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-09-30 22:13:48 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-09-30 22:13:48 (7666) [INFO] Running: /usr/bin/yum list extras * 2024-09-30 22:13:48 (7667) [INFO] * 2024-09-30 22:13:52 (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 22:13:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-09-30 22:13:52 (7666) [INFO] Running: /usr/bin/yum clean all * 2024-09-30 22:13:52 (7667) [INFO] * 2024-09-30 22:13:52 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-09-30 22:13:52 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-09-30 22:13:52 (7680) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-09-30 22:13:52 (7680) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-09-30 22:13:52 (7680) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-09-30 22:13:52 (7680) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-09-30 22:13:52 (7680) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-09-30 22:13:52 (7680) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-09-30 22:13:52 (7680) [INFO] : mysql-tools-community mysql57-community updates * 2024-09-30 22:13:52 (7680) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-09-30 22:13:52 (7680) [INFO] Cleaning up list of fastest mirrors * 2024-09-30 22:13:52 (7680) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-09-30 22:13:52 (7697) [INFO] * 2024-09-30 22:13: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-09-30 22:13: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-09-30 22:13:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-09-30 22:13:56 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yCx1k9Jm4s/ea_profile.json * 2024-09-30 22:13: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/yCx1k9Jm4s/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804. * 2024-09-30 22:13:57 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-01 22:13:43 (9008) [INFO] Self-update of script version 54 requested. * 2024-10-01 22:13:43 (9013) [INFO] Newer version of script found. Downloading. * 2024-10-01 22:13:43 (9022) [INFO] Script update to version 55 successful. * 2024-10-01 22:13:45 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-01 22:13:45 (7668) [INFO] * 2024-10-01 22:13:49 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-01 22:13:49 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-01 22:13:49 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-01 22:13:49 (7668) [INFO] * 2024-10-01 22:13:55 (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 22:13:55 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-01 22:13:55 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-01 22:13:55 (7668) [INFO] * 2024-10-01 22:13:55 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-01 22:13:55 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-01 22:13:55 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-01 22:13:55 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-01 22:13:55 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-01 22:13:55 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-01 22:13:55 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-01 22:13:55 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-01 22:13:55 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-01 22:13:55 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-01 22:13:55 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-01 22:13:55 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-01 22:13:55 (7698) [INFO] * 2024-10-01 22:13: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-01 22:13: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-01 22:13:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-01 22:14:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tijV8IcyKW/ea_profile.json * 2024-10-01 22:14: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/tijV8IcyKW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-01 22:14:02 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-02 22:14:25 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-02 22:14:25 (9031) [INFO] Script is up to date. * 2024-10-02 22:14:27 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-02 22:14:27 (7668) [INFO] * 2024-10-02 22:14:33 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-02 22:14:33 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-02 22:14:33 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-02 22:14:33 (7668) [INFO] * 2024-10-02 22:14: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-10-02 22:14:39 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-02 22:14:39 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-02 22:14:39 (7668) [INFO] * 2024-10-02 22:14:39 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-02 22:14:40 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-02 22:14:40 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-02 22:14:40 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-02 22:14:40 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-02 22:14:40 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-02 22:14:40 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-02 22:14:40 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-02 22:14:40 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-02 22:14:40 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-02 22:14:40 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-02 22:14:40 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-02 22:14:40 (7698) [INFO] * 2024-10-02 22:14:42 (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 22:14:42 (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 22:14:42 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-02 22:14:43 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AIBX_J74xT/ea_profile.json * 2024-10-02 22:14: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/AIBX_J74xT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-02 22:14:44 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-03 22:13:48 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-03 22:13:49 (9031) [INFO] Script is up to date. * 2024-10-03 22:13:50 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-03 22:13:50 (7668) [INFO] * 2024-10-03 22:13:54 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-03 22:13:54 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-03 22:13:54 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-03 22:13:54 (7668) [INFO] * 2024-10-03 22:14:01 (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 22:14:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-03 22:14:01 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-03 22:14:01 (7668) [INFO] * 2024-10-03 22:14:02 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-03 22:14:02 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-03 22:14:02 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-03 22:14:02 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-03 22:14:02 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-03 22:14:02 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-03 22:14:02 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-03 22:14:02 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-03 22:14:02 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-03 22:14:02 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-03 22:14:02 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-03 22:14:02 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-03 22:14:02 (7698) [INFO] * 2024-10-03 22:14: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-03 22:14: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-03 22:14:05 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-03 22:14:06 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QeizYNFNOZ/ea_profile.json * 2024-10-03 22:14:07 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QeizYNFNOZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-03 22:14:07 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-04 22:13:53 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-04 22:13:53 (9031) [INFO] Script is up to date. * 2024-10-04 22:13:55 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-04 22:13:55 (7668) [INFO] * 2024-10-04 22:14:02 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-04 22:14:02 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-04 22:14:02 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-04 22:14:02 (7668) [INFO] * 2024-10-04 22:14:14 (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 22:14:14 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-04 22:14:14 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-04 22:14:14 (7668) [INFO] * 2024-10-04 22:14:15 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-04 22:14:15 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-04 22:14:15 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-04 22:14:15 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-04 22:14:15 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-04 22:14:15 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-04 22:14:15 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-04 22:14:15 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-04 22:14:15 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-04 22:14:15 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-04 22:14:15 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-04 22:14:15 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-04 22:14:15 (7698) [INFO] * 2024-10-04 22:14:18 (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 22:14:18 (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 22:14:19 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-04 22:14:20 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wy5jyj0WCO/ea_profile.json * 2024-10-04 22:14:22 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wy5jyj0WCO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-04 22:14:22 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-05 22:14:38 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-05 22:14:38 (9031) [INFO] Script is up to date. * 2024-10-05 22:14:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-05 22:14:39 (7668) [INFO] * 2024-10-05 22:14:43 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-05 22:14:43 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-05 22:14:43 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-05 22:14:43 (7668) [INFO] * 2024-10-05 22:14: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-05 22:14:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-05 22:14:48 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-05 22:14:48 (7668) [INFO] * 2024-10-05 22:14:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-05 22:14:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-05 22:14:48 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-05 22:14:48 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-05 22:14:48 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-05 22:14:48 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-05 22:14:48 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-05 22:14:48 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-05 22:14:48 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-05 22:14:48 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-05 22:14:48 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-05 22:14:48 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-05 22:14:48 (7698) [INFO] * 2024-10-05 22:14: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-05 22:14: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-05 22:14:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-05 22:14:52 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xhvaPwy8zd/ea_profile.json * 2024-10-05 22:14: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/xhvaPwy8zd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-05 22:14:53 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-06 22:14:32 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-06 22:14:32 (9031) [INFO] Script is up to date. * 2024-10-06 22:14:33 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-06 22:14:33 (7668) [INFO] * 2024-10-06 22:14:36 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-06 22:14:36 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-06 22:14:36 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-06 22:14:36 (7668) [INFO] * 2024-10-06 22:14: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-06 22:14:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-06 22:14:42 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-06 22:14:42 (7668) [INFO] * 2024-10-06 22:14:42 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-06 22:14:43 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-06 22:14:43 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-06 22:14:43 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-06 22:14:43 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-06 22:14:43 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-06 22:14:43 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-06 22:14:43 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-06 22:14:43 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-06 22:14:43 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-06 22:14:43 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-06 22:14:43 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-06 22:14:43 (7698) [INFO] * 2024-10-06 22:14: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-06 22:14: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-06 22:14:45 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-06 22:14:46 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/d4Q9b9XES9/ea_profile.json * 2024-10-06 22:14: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/d4Q9b9XES9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-06 22:14:48 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-07 22:13:43 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-07 22:13:43 (9031) [INFO] Script is up to date. * 2024-10-07 22:13:45 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-07 22:13:45 (7668) [INFO] * 2024-10-07 22:13:48 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-07 22:13:48 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-07 22:13:48 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-07 22:13:48 (7668) [INFO] * 2024-10-07 22:13:56 (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 22:13:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-07 22:13:56 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-07 22:13:56 (7668) [INFO] * 2024-10-07 22:13:56 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-07 22:13:56 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-07 22:13:56 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-07 22:13:56 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-07 22:13:56 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-07 22:13:56 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-07 22:13:56 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-07 22:13:56 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-07 22:13:56 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-07 22:13:56 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-07 22:13:56 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-07 22:13:56 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-07 22:13:56 (7698) [INFO] * 2024-10-07 22:13: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 22:13: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 22:14:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-07 22:14:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jI9X4MyZeY/ea_profile.json * 2024-10-07 22:14: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/jI9X4MyZeY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-07 22:14:02 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-08 22:13:44 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-08 22:13:45 (9031) [INFO] Script is up to date. * 2024-10-08 22:13:46 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-08 22:13:46 (7668) [INFO] * 2024-10-08 22:13:51 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-08 22:13:51 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-08 22:13:51 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-08 22:13:51 (7668) [INFO] * 2024-10-08 22:13:57 (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 22:13:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-08 22:13:57 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-08 22:13:57 (7668) [INFO] * 2024-10-08 22:13:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-08 22:13:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-08 22:13:57 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-08 22:13:57 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-08 22:13:57 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-08 22:13:57 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-08 22:13:57 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-08 22:13:57 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-08 22:13:57 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-08 22:13:57 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-08 22:13:57 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-08 22:13:57 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-08 22:13:57 (7698) [INFO] * 2024-10-08 22:13: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-08 22:13: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-08 22:13:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-08 22:14:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rbPncvbRnn/ea_profile.json * 2024-10-08 22:14: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/rbPncvbRnn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-08 22:14:01 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-09 22:13:38 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-09 22:13:38 (9031) [INFO] Script is up to date. * 2024-10-09 22:13:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-09 22:13:39 (7668) [INFO] * 2024-10-09 22:13:42 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-09 22:13:42 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-09 22:13:42 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-09 22:13:42 (7668) [INFO] * 2024-10-09 22:13: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-09 22:13:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-09 22:13:48 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-09 22:13:48 (7668) [INFO] * 2024-10-09 22:13:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-09 22:13:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-09 22:13:48 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-09 22:13:48 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-09 22:13:48 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-09 22:13:48 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-09 22:13:48 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-09 22:13:48 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-09 22:13:48 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-09 22:13:48 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-09 22:13:48 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-09 22:13:48 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-09 22:13:48 (7698) [INFO] * 2024-10-09 22:13:51 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-09 22:13: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-10-09 22:13:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-09 22:13:52 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LkbnJ1yAOo/ea_profile.json * 2024-10-09 22:13: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/LkbnJ1yAOo/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-09 22:13:53 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-10 22:13:45 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-10 22:13:45 (9031) [INFO] Script is up to date. * 2024-10-10 22:13:47 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-10 22:13:47 (7668) [INFO] * 2024-10-10 22:13:54 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-10 22:13:54 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-10 22:13:54 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-10 22:13:54 (7668) [INFO] * 2024-10-10 22:14:02 (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 22:14:02 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-10 22:14:02 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-10 22:14:02 (7668) [INFO] * 2024-10-10 22:14:02 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-10 22:14:02 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-10 22:14:02 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-10 22:14:02 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-10 22:14:02 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-10 22:14:02 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-10 22:14:02 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-10 22:14:02 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-10 22:14:02 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-10 22:14:02 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-10 22:14:02 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-10 22:14:02 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-10 22:14:02 (7698) [INFO] * 2024-10-10 22:14:05 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-10 22:14:05 (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 22:14:05 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-10 22:14:06 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3VMD3GOsUX/ea_profile.json * 2024-10-10 22:14: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/3VMD3GOsUX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-10 22:14:09 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-11 22:13:45 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-11 22:13:45 (9031) [INFO] Script is up to date. * 2024-10-11 22:13:47 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-11 22:13:47 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-11 22:13:47 (7668) [INFO] * 2024-10-11 22:13:50 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-11 22:13:50 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-11 22:13:50 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-11 22:13:50 (7668) [INFO] * 2024-10-11 22:13:57 (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 22:13:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-11 22:13:57 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-11 22:13:57 (7668) [INFO] * 2024-10-11 22:13:58 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-11 22:13:58 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-11 22:13:58 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-11 22:13:58 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-11 22:13:58 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-11 22:13:58 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-11 22:13:58 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-11 22:13:58 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-11 22:13:58 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-11 22:13:58 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-11 22:13:58 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-11 22:13:58 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-11 22:13:58 (7698) [INFO] * 2024-10-11 22:14:00 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-11 22:14: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-10-11 22:14:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-11 22:14:01 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a0LyQYoJ1S/ea_profile.json * 2024-10-11 22:14: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/a0LyQYoJ1S/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-11 22:14:03 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-12 22:14:37 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-12 22:14:37 (9031) [INFO] Script is up to date. * 2024-10-12 22:14:38 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-12 22:14:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-12 22:14:38 (7668) [INFO] * 2024-10-12 22:14:42 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-12 22:14:42 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-12 22:14:42 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-12 22:14:42 (7668) [INFO] * 2024-10-12 22:14: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-12 22:14:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-12 22:14:47 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-12 22:14:47 (7668) [INFO] * 2024-10-12 22:14:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-12 22:14:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-12 22:14:48 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-12 22:14:48 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-12 22:14:48 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-12 22:14:48 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-12 22:14:48 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-12 22:14:48 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-12 22:14:48 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-12 22:14:48 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-12 22:14:48 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-12 22:14:48 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-12 22:14:48 (7698) [INFO] * 2024-10-12 22:14:51 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-12 22:14: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-10-12 22:14:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-12 22:14:52 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KAaeS9BkQe/ea_profile.json * 2024-10-12 22:14: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/KAaeS9BkQe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-12 22:14:54 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-13 22:14:30 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-13 22:14:30 (9031) [INFO] Script is up to date. * 2024-10-13 22:14:32 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-13 22:14:32 (7668) [INFO] * 2024-10-13 22:14:36 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-13 22:14:36 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-13 22:14:36 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-13 22:14:36 (7668) [INFO] * 2024-10-13 22:14: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 22:14:41 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-13 22:14:41 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-13 22:14:41 (7668) [INFO] * 2024-10-13 22:14:41 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-13 22:14:42 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-13 22:14:42 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-13 22:14:42 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-13 22:14:42 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-13 22:14:42 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-13 22:14:42 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-13 22:14:42 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-13 22:14:42 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-13 22:14:42 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-13 22:14:42 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-13 22:14:42 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-13 22:14:42 (7698) [INFO] * 2024-10-13 22:14:44 (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 22:14:44 (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 22:14:44 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-13 22:14:45 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lY7Vlyoct9/ea_profile.json * 2024-10-13 22:14:46 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lY7Vlyoct9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-13 22:14:46 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-14 22:13:44 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-14 22:13:45 (9031) [INFO] Script is up to date. * 2024-10-14 22:13:46 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-14 22:13:46 (7668) [INFO] * 2024-10-14 22:13:49 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-14 22:13:49 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-14 22:13:49 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-14 22:13:49 (7668) [INFO] * 2024-10-14 22:13: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-14 22:13:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-14 22:13:54 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-14 22:13:54 (7668) [INFO] * 2024-10-14 22:13:55 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-14 22:13:55 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-14 22:13:55 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-14 22:13:55 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-14 22:13:55 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-14 22:13:55 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-14 22:13:55 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-14 22:13:55 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-14 22:13:55 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-14 22:13:55 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-14 22:13:55 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-14 22:13:55 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-14 22:13:55 (7698) [INFO] * 2024-10-14 22:13: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-14 22:13: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-14 22:13:57 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-14 22:13:58 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/h_FRKBn2q0/ea_profile.json * 2024-10-14 22:14: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/h_FRKBn2q0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-14 22:14:00 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-15 22:13:45 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-15 22:13:46 (9031) [INFO] Script is up to date. * 2024-10-15 22:13:47 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-15 22:13:47 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-15 22:13:47 (7668) [INFO] * 2024-10-15 22:13:50 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-15 22:13:50 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-15 22:13:50 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-15 22:13:50 (7668) [INFO] * 2024-10-15 22:13:56 (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 22:13:56 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-15 22:13:56 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-15 22:13:56 (7668) [INFO] * 2024-10-15 22:13:56 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-15 22:13:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-15 22:13:57 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-15 22:13:57 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-15 22:13:57 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-15 22:13:57 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-15 22:13:57 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-15 22:13:57 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-15 22:13:57 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-15 22:13:57 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-15 22:13:57 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-15 22:13:57 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-15 22:13:57 (7698) [INFO] * 2024-10-15 22:13: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-15 22:13: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-15 22:13:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-15 22:14:00 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zpWy5aC9cf/ea_profile.json * 2024-10-15 22:14: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/zpWy5aC9cf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-15 22:14:02 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-16 22:14:27 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-16 22:14:27 (9031) [INFO] Script is up to date. * 2024-10-16 22:14:29 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-16 22:14:30 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-16 22:14:30 (7668) [INFO] * 2024-10-16 22:14:34 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-16 22:14:34 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-16 22:14:34 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-16 22:14:34 (7668) [INFO] * 2024-10-16 22:14: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-16 22:14:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-16 22:14:42 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-16 22:14:42 (7668) [INFO] * 2024-10-16 22:14:42 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-16 22:14:42 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-16 22:14:42 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-16 22:14:42 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-16 22:14:42 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-16 22:14:42 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-16 22:14:42 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-16 22:14:42 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-16 22:14:42 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-16 22:14:42 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-16 22:14:42 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-16 22:14:42 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-16 22:14:42 (7698) [INFO] * 2024-10-16 22:14: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-16 22:14: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-16 22:14:45 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-16 22:14:46 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fYDEl1bGzO/ea_profile.json * 2024-10-16 22:14:47 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fYDEl1bGzO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-16 22:14:47 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-17 22:14:52 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-17 22:14:52 (9031) [INFO] Script is up to date. * 2024-10-17 22:14:53 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-17 22:14:54 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-17 22:14:54 (7668) [INFO] * 2024-10-17 22:14:58 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-17 22:14:58 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-17 22:14:58 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-17 22:14:58 (7668) [INFO] * 2024-10-17 22:15:12 (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 22:15:12 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-17 22:15:12 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-17 22:15:12 (7668) [INFO] * 2024-10-17 22:15:12 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-17 22:15:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-17 22:15:12 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-17 22:15:12 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-17 22:15:12 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-17 22:15:12 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-17 22:15:12 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-17 22:15:12 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-17 22:15:12 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-17 22:15:12 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-17 22:15:13 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-17 22:15:13 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-17 22:15:13 (7698) [INFO] * 2024-10-17 22:15:16 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-17 22:15:16 (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 22:15:17 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-17 22:15:18 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zTD0C9zbqz/ea_profile.json * 2024-10-17 22:15:19 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zTD0C9zbqz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-17 22:15:19 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-18 22:13:43 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-18 22:13:43 (9031) [INFO] Script is up to date. * 2024-10-18 22:13:44 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-18 22:13:44 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-18 22:13:44 (7668) [INFO] * 2024-10-18 22:13:48 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-18 22:13:48 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-18 22:13:48 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-18 22:13:48 (7668) [INFO] * 2024-10-18 22:13:57 (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 22:13:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-18 22:13:57 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-18 22:13:57 (7668) [INFO] * 2024-10-18 22:13:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-18 22:13:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-18 22:13:57 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-18 22:13:57 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-18 22:13:57 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-18 22:13:57 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-18 22:13:57 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-18 22:13:57 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-18 22:13:57 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-18 22:13:57 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-18 22:13:57 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-18 22:13:58 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-18 22:13:58 (7698) [INFO] * 2024-10-18 22:14:01 (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 22:14:01 (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 22:14:01 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-18 22:14:02 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qp2YQE85x4/ea_profile.json * 2024-10-18 22:14: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/qp2YQE85x4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-18 22:14:04 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-19 22:14:38 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-19 22:14:38 (9031) [INFO] Script is up to date. * 2024-10-19 22:14:39 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-19 22:14:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-19 22:14:40 (7668) [INFO] * 2024-10-19 22:14:42 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-19 22:14:42 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-19 22:14:42 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-19 22:14:42 (7668) [INFO] * 2024-10-19 22:14: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-19 22:14:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-19 22:14:49 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-19 22:14:49 (7668) [INFO] * 2024-10-19 22:14:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-19 22:14:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-19 22:14:49 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-19 22:14:49 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-19 22:14:49 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-19 22:14:49 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-19 22:14:49 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-19 22:14:49 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-19 22:14:49 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-19 22:14:49 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-19 22:14:49 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-19 22:14:49 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-19 22:14:49 (7698) [INFO] * 2024-10-19 22:14: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 22:14: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 22:14:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-19 22:14:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8r9qRvC_l8/ea_profile.json * 2024-10-19 22:14:55 (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/8r9qRvC_l8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-19 22:14:55 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-20 22:14:42 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-20 22:14:42 (9031) [INFO] Script is up to date. * 2024-10-20 22:14:43 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-20 22:14:43 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-20 22:14:43 (7668) [INFO] * 2024-10-20 22:14:47 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-20 22:14:47 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-20 22:14:47 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-20 22:14:47 (7668) [INFO] * 2024-10-20 22:14:52 (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 22:14:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-20 22:14:52 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-20 22:14:52 (7668) [INFO] * 2024-10-20 22:14:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-20 22:14:52 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-20 22:14:52 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-20 22:14:52 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-20 22:14:52 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-20 22:14:52 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-20 22:14:52 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-20 22:14:52 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-20 22:14:52 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-20 22:14:52 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-20 22:14:52 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-20 22:14:52 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-20 22:14:52 (7698) [INFO] * 2024-10-20 22:14: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-20 22:14: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-20 22:14:54 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-20 22:14:55 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0yfiFJGvn9/ea_profile.json * 2024-10-20 22:14: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/0yfiFJGvn9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-20 22:14:56 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-21 22:13:50 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-21 22:13:50 (9031) [INFO] Script is up to date. * 2024-10-21 22:13:52 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-21 22:13:52 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-21 22:13:52 (7668) [INFO] * 2024-10-21 22:13:55 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-21 22:13:55 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-21 22:13:55 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-21 22:13:55 (7668) [INFO] * 2024-10-21 22:14:01 (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 22:14:01 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-21 22:14:01 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-21 22:14:01 (7668) [INFO] * 2024-10-21 22:14:01 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-21 22:14:01 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-21 22:14:01 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-21 22:14:01 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-21 22:14:01 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-21 22:14:01 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-21 22:14:01 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-21 22:14:01 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-21 22:14:01 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-21 22:14:01 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-21 22:14:01 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-21 22:14:01 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-21 22:14:01 (7698) [INFO] * 2024-10-21 22:14: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-21 22:14: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-21 22:14:04 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-21 22:14:05 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X6ivKtNOXI/ea_profile.json * 2024-10-21 22:14:07 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/X6ivKtNOXI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-21 22:14:07 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-22 22:13:37 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-22 22:13:37 (9031) [INFO] Script is up to date. * 2024-10-22 22:13:38 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-22 22:13:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-22 22:13:38 (7668) [INFO] * 2024-10-22 22:13:41 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-22 22:13:41 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-22 22:13:41 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-22 22:13:41 (7668) [INFO] * 2024-10-22 22:13: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-22 22:13:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-22 22:13:48 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-22 22:13:48 (7668) [INFO] * 2024-10-22 22:13:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-22 22:13:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-22 22:13:48 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-22 22:13:48 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-22 22:13:48 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-22 22:13:48 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-22 22:13:48 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-22 22:13:48 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-22 22:13:48 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-22 22:13:48 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-22 22:13:48 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-22 22:13:48 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-22 22:13:48 (7698) [INFO] * 2024-10-22 22:13:51 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-22 22:13: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-10-22 22:13:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-22 22:13:52 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dGrZiDhta5/ea_profile.json * 2024-10-22 22:13: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/dGrZiDhta5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-22 22:13:53 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-23 22:13:40 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-23 22:13:40 (9031) [INFO] Script is up to date. * 2024-10-23 22:13:43 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-23 22:13:43 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-23 22:13:43 (7668) [INFO] * 2024-10-23 22:13:47 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-23 22:13:47 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-23 22:13:47 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-23 22:13:47 (7668) [INFO] * 2024-10-23 22:13:52 (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 22:13:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-23 22:13:52 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-23 22:13:52 (7668) [INFO] * 2024-10-23 22:13:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-23 22:13:53 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-23 22:13:53 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-23 22:13:53 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-23 22:13:53 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-23 22:13:53 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-23 22:13:53 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-23 22:13:53 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-23 22:13:53 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-23 22:13:53 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-23 22:13:53 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-23 22:13:53 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-23 22:13:53 (7698) [INFO] * 2024-10-23 22:13: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-23 22:13: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-23 22:13:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-23 22:13:56 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cpms912zYi/ea_profile.json * 2024-10-23 22:13: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/cpms912zYi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-23 22:13:57 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-24 22:14:17 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-24 22:14:17 (9031) [INFO] Script is up to date. * 2024-10-24 22:14:18 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-24 22:14:18 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-24 22:14:18 (7668) [INFO] * 2024-10-24 22:14:21 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-24 22:14:21 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-24 22:14:21 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-24 22:14:21 (7668) [INFO] * 2024-10-24 22:14:27 (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 22:14:27 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-24 22:14:27 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-24 22:14:27 (7668) [INFO] * 2024-10-24 22:14:27 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-24 22:14:28 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-24 22:14:28 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-24 22:14:28 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-24 22:14:28 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-24 22:14:28 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-24 22:14:28 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-24 22:14:28 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-24 22:14:28 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-24 22:14:28 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-24 22:14:28 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-24 22:14:28 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-24 22:14:28 (7698) [INFO] * 2024-10-24 22:14: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-24 22:14: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-24 22:14:30 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-24 22:14:31 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/455Gzo_bsF/ea_profile.json * 2024-10-24 22:14: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/455Gzo_bsF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-24 22:14:33 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-25 22:13:39 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-25 22:13:39 (9031) [INFO] Script is up to date. * 2024-10-25 22:13:40 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-25 22:13:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-25 22:13:40 (7668) [INFO] * 2024-10-25 22:13:46 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-25 22:13:46 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-25 22:13:46 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-25 22:13:46 (7668) [INFO] * 2024-10-25 22:13:52 (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 22:13:52 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-25 22:13:52 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-25 22:13:52 (7668) [INFO] * 2024-10-25 22:13:52 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-25 22:13:52 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-25 22:13:52 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-25 22:13:52 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-25 22:13:52 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-25 22:13:52 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-25 22:13:52 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-25 22:13:52 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-25 22:13:52 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-25 22:13:52 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-25 22:13:52 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-25 22:13:52 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-25 22:13:52 (7698) [INFO] * 2024-10-25 22:13: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-25 22:13: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-25 22:13:55 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-25 22:13:56 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TFrvaPvmSL/ea_profile.json * 2024-10-25 22:13: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/TFrvaPvmSL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-25 22:13:58 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-26 22:14:33 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-26 22:14:33 (9031) [INFO] Script is up to date. * 2024-10-26 22:14:34 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-26 22:14:34 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-26 22:14:34 (7668) [INFO] * 2024-10-26 22:14:40 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-26 22:14:40 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-26 22:14:40 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-26 22:14:40 (7668) [INFO] * 2024-10-26 22:14: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-26 22:14:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-26 22:14:45 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-26 22:14:45 (7668) [INFO] * 2024-10-26 22:14:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-26 22:14:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-26 22:14:46 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-26 22:14:46 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-26 22:14:46 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-26 22:14:46 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-26 22:14:46 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-26 22:14:46 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-26 22:14:46 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-26 22:14:46 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-26 22:14:46 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-26 22:14:46 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-26 22:14:46 (7698) [INFO] * 2024-10-26 22:14: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-26 22:14: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-26 22:14:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-26 22:14:49 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/6GRgqMEAdg/ea_profile.json * 2024-10-26 22:14: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/6GRgqMEAdg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-26 22:14:50 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-27 22:14:29 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-27 22:14:29 (9031) [INFO] Script is up to date. * 2024-10-27 22:14:31 (230) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-27 22:14:31 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-27 22:14:31 (7668) [INFO] * 2024-10-27 22:14:34 (675) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-27 22:14:34 (682) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-27 22:14:34 (7667) [INFO] Running: /usr/bin/yum list extras * 2024-10-27 22:14:34 (7668) [INFO] * 2024-10-27 22:14: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-10-27 22:14:39 (1996) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-27 22:14:39 (7667) [INFO] Running: /usr/bin/yum clean all * 2024-10-27 22:14:39 (7668) [INFO] * 2024-10-27 22:14:39 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-27 22:14:39 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-27 22:14:39 (7681) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-27 22:14:39 (7681) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-27 22:14:39 (7681) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-27 22:14:39 (7681) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-27 22:14:39 (7681) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-27 22:14:39 (7681) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-27 22:14:39 (7681) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-27 22:14:39 (7681) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-27 22:14:39 (7681) [INFO] Cleaning up list of fastest mirrors * 2024-10-27 22:14:39 (7681) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-27 22:14:39 (7698) [INFO] * 2024-10-27 22:14:42 (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 22:14:42 (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 22:14:42 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-27 22:14:43 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wi6pbcPxyq/ea_profile.json * 2024-10-27 22:14: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/Wi6pbcPxyq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805. * 2024-10-27 22:14:44 (354) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-28 22:13:44 (9009) [INFO] Self-update of script version 55 requested. * 2024-10-28 22:13:44 (9014) [INFO] Newer version of script found. Downloading. * 2024-10-28 22:13:45 (9023) [INFO] Script update to version 56 successful. * 2024-10-28 22:13:47 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-28 22:13:47 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-28 22:13:47 (7662) [INFO] * 2024-10-28 22:13:50 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-28 22:13:50 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-28 22:13:50 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-28 22:13:50 (7662) [INFO] * 2024-10-28 22:13:55 (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-28 22:13:55 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-28 22:13:55 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-28 22:13:55 (7662) [INFO] * 2024-10-28 22:13:55 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-28 22:13:56 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-28 22:13:56 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-28 22:13:56 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-28 22:13:56 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-28 22:13:56 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-28 22:13:56 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-28 22:13:56 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-28 22:13:56 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-28 22:13:56 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-28 22:13:56 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-28 22:13:56 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-28 22:13:56 (7692) [INFO] * 2024-10-28 22:13:58 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-10-28 22:13:58 (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-28 22:13:58 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-28 22:13:59 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wt_r8xHFf_/ea_profile.json * 2024-10-28 22:14:01 (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/Wt_r8xHFf_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-10-28 22:14:01 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-29 22:13:47 (8998) [INFO] Self-update of script version 56 requested. * 2024-10-29 22:13:47 (9020) [INFO] Script is up to date. * 2024-10-29 22:13:49 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-29 22:13:49 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-29 22:13:49 (7662) [INFO] * 2024-10-29 22:13:53 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-29 22:13:53 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-29 22:13:53 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-29 22:13:53 (7662) [INFO] * 2024-10-29 22:13:58 (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 22:13:58 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-29 22:13:58 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-29 22:13:58 (7662) [INFO] * 2024-10-29 22:13:59 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-29 22:13:59 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-29 22:13:59 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-29 22:13:59 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-29 22:13:59 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-29 22:13:59 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-29 22:13:59 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-29 22:13:59 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-29 22:13:59 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-29 22:13:59 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-29 22:13:59 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-29 22:13:59 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-29 22:13:59 (7692) [INFO] * 2024-10-29 22:14:01 (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 22:14:01 (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 22:14:01 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-29 22:14:02 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2eTx79sQSl/ea_profile.json * 2024-10-29 22:14: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/2eTx79sQSl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-10-29 22:14:03 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-30 22:13:40 (8998) [INFO] Self-update of script version 56 requested. * 2024-10-30 22:13:40 (9020) [INFO] Script is up to date. * 2024-10-30 22:13:41 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-30 22:13:41 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-30 22:13:41 (7662) [INFO] * 2024-10-30 22:13:45 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-30 22:13:45 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-30 22:13:45 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-30 22:13:45 (7662) [INFO] * 2024-10-30 22:13:51 (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 22:13:51 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-30 22:13:51 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-30 22:13:51 (7662) [INFO] * 2024-10-30 22:13:51 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-30 22:13:51 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-30 22:13:51 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-30 22:13:51 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-30 22:13:51 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-30 22:13:51 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-30 22:13:51 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-30 22:13:51 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-30 22:13:51 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-30 22:13:51 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-30 22:13:51 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-30 22:13:51 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-30 22:13:51 (7692) [INFO] * 2024-10-30 22:13:53 (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 22:13:53 (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 22:13:54 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-30 22:13:55 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/46Ml7YRZDz/ea_profile.json * 2024-10-30 22:13:56 (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/46Ml7YRZDz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-10-30 22:13:56 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-10-31 22:14:40 (8998) [INFO] Self-update of script version 56 requested. * 2024-10-31 22:14:40 (9020) [INFO] Script is up to date. * 2024-10-31 22:14:41 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-10-31 22:14:41 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-10-31 22:14:41 (7662) [INFO] * 2024-10-31 22:14:44 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-10-31 22:14:44 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-10-31 22:14:44 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-10-31 22:14:44 (7662) [INFO] * 2024-10-31 22:14:51 (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 22:14:51 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-10-31 22:14:51 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-10-31 22:14:51 (7662) [INFO] * 2024-10-31 22:14:51 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-10-31 22:14:51 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-10-31 22:14:51 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-10-31 22:14:51 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-10-31 22:14:51 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-10-31 22:14:51 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-10-31 22:14:51 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-10-31 22:14:51 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-10-31 22:14:51 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-10-31 22:14:51 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-10-31 22:14:51 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-10-31 22:14:51 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-10-31 22:14:51 (7692) [INFO] * 2024-10-31 22:14: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-31 22:14: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-31 22:14:54 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-10-31 22:14:55 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Og3vkyAk9X/ea_profile.json * 2024-10-31 22:14: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/Og3vkyAk9X/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-10-31 22:14:57 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-01 22:13:43 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-01 22:13:43 (9020) [INFO] Script is up to date. * 2024-11-01 22:13:44 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-01 22:13:44 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-01 22:13:44 (7662) [INFO] * 2024-11-01 22:13:48 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-01 22:13:48 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-01 22:13:48 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-01 22:13:48 (7662) [INFO] * 2024-11-01 22:13: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-11-01 22:13:53 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-01 22:13:53 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-01 22:13:53 (7662) [INFO] * 2024-11-01 22:13:53 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-01 22:13:54 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-01 22:13:54 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-01 22:13:54 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-01 22:13:54 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-01 22:13:54 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-01 22:13:54 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-01 22:13:54 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-01 22:13:54 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-01 22:13:54 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-01 22:13:54 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-01 22:13:54 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-01 22:13:54 (7692) [INFO] * 2024-11-01 22:13:56 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-01 22:13:56 (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 22:13:56 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-01 22:13:57 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uDaFt8Dp75/ea_profile.json * 2024-11-01 22:13:59 (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/uDaFt8Dp75/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-01 22:13:59 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-02 22:14:31 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-02 22:14:31 (9020) [INFO] Script is up to date. * 2024-11-02 22:14:32 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-02 22:14:32 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-02 22:14:32 (7662) [INFO] * 2024-11-02 22:14:35 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-02 22:14:35 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-02 22:14:35 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-02 22:14:35 (7662) [INFO] * 2024-11-02 22:14:40 (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 22:14:40 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-02 22:14:40 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-02 22:14:40 (7662) [INFO] * 2024-11-02 22:14:40 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-02 22:14:40 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-02 22:14:40 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-02 22:14:40 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-02 22:14:40 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-02 22:14:40 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-02 22:14:40 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-02 22:14:40 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-02 22:14:40 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-02 22:14:40 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-02 22:14:40 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-02 22:14:40 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-02 22:14:40 (7692) [INFO] * 2024-11-02 22:14:42 (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 22:14:42 (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 22:14:42 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-02 22:14:43 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/t8K_UfuPYV/ea_profile.json * 2024-11-02 22:14:45 (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/t8K_UfuPYV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-02 22:14:45 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-03 22:14:37 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-03 22:14:37 (9020) [INFO] Script is up to date. * 2024-11-03 22:14:38 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-03 22:14:38 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-03 22:14:38 (7662) [INFO] * 2024-11-03 22:14:41 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-03 22:14:41 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-03 22:14:41 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-03 22:14:41 (7662) [INFO] * 2024-11-03 22:14: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-03 22:14:46 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-03 22:14:46 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-03 22:14:46 (7662) [INFO] * 2024-11-03 22:14:46 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-03 22:14:46 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-03 22:14:46 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-03 22:14:46 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-03 22:14:46 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-03 22:14:46 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-03 22:14:46 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-03 22:14:46 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-03 22:14:46 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-03 22:14:46 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-03 22:14:46 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-03 22:14:46 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-03 22:14:46 (7692) [INFO] * 2024-11-03 22:14:48 (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 22:14:48 (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 22:14:48 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-03 22:14:49 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i_II2WfyG0/ea_profile.json * 2024-11-03 22:14:50 (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/i_II2WfyG0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-03 22:14:50 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-04 22:13:42 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-04 22:13:43 (9020) [INFO] Script is up to date. * 2024-11-04 22:13:44 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-04 22:13:44 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-04 22:13:44 (7662) [INFO] * 2024-11-04 22:13:46 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-04 22:13:46 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-04 22:13:46 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-04 22:13:46 (7662) [INFO] * 2024-11-04 22:13: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-11-04 22:13:53 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-04 22:13:53 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-04 22:13:53 (7662) [INFO] * 2024-11-04 22:13:53 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-04 22:13:53 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-04 22:13:53 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-04 22:13:53 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-04 22:13:53 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-04 22:13:53 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-04 22:13:53 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-04 22:13:53 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-04 22:13:53 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-04 22:13:53 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-04 22:13:53 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-04 22:13:53 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-04 22:13:53 (7692) [INFO] * 2024-11-04 22:13: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 22:13: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 22:13:56 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-04 22:13:57 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_ihWEqpLc1/ea_profile.json * 2024-11-04 22:13:58 (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/_ihWEqpLc1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-04 22:13:58 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-05 22:14:16 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-05 22:14:16 (9020) [INFO] Script is up to date. * 2024-11-05 22:14:17 (264) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-05 22:14:17 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-05 22:14:17 (7662) [INFO] * 2024-11-05 22:14:20 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-05 22:14:20 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-05 22:14:20 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-05 22:14:20 (7662) [INFO] * 2024-11-05 22:14:25 (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 22:14:25 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-05 22:14:25 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-05 22:14:25 (7662) [INFO] * 2024-11-05 22:14:25 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-05 22:14:26 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-05 22:14:26 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-05 22:14:26 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-05 22:14:26 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-05 22:14:26 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-05 22:14:26 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-05 22:14:26 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-05 22:14:26 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-05 22:14:26 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-05 22:14:26 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-05 22:14:26 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-05 22:14:26 (7692) [INFO] * 2024-11-05 22:14:29 (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 22:14:29 (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 22:14:29 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-05 22:14:30 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cCl4J9janu/ea_profile.json * 2024-11-05 22:14:32 (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/cCl4J9janu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-05 22:14:32 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-06 22:13:42 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-06 22:13:42 (9020) [INFO] Script is up to date. * 2024-11-06 22:13:44 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-06 22:13:44 (7662) [INFO] * 2024-11-06 22:13:48 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-06 22:13:48 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-06 22:13:48 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-06 22:13:48 (7662) [INFO] * 2024-11-06 22:13:55 (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 22:13:55 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-06 22:13:55 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-06 22:13:55 (7662) [INFO] * 2024-11-06 22:13:56 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-06 22:13:56 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-06 22:13:56 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-06 22:13:56 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-06 22:13:56 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-06 22:13:56 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-06 22:13:56 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-06 22:13:56 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-06 22:13:56 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-06 22:13:56 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-06 22:13:56 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-06 22:13:56 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-06 22:13:56 (7692) [INFO] * 2024-11-06 22:13:58 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-06 22:13:58 (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 22:13:58 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-06 22:13:59 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l3Eg3Vrb52/ea_profile.json * 2024-11-06 22:14:00 (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/l3Eg3Vrb52/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-06 22:14:00 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-07 22:13:46 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-07 22:13:47 (9020) [INFO] Script is up to date. * 2024-11-07 22:13:48 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-07 22:13:48 (7662) [INFO] * 2024-11-07 22:13:51 (3708) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-07 22:13:51 (3715) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-07 22:13:51 (7661) [INFO] Running: /usr/bin/yum list extras * 2024-11-07 22:13:51 (7662) [INFO] * 2024-11-07 22:13:57 (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 22:13:57 (5457) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-07 22:13:57 (7661) [INFO] Running: /usr/bin/yum clean all * 2024-11-07 22:13:57 (7662) [INFO] * 2024-11-07 22:13:57 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-07 22:13:57 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-07 22:13:57 (7675) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-07 22:13:57 (7675) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-07 22:13:57 (7675) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-07 22:13:57 (7675) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-07 22:13:57 (7675) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-07 22:13:57 (7675) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-07 22:13:57 (7675) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-07 22:13:57 (7675) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-07 22:13:57 (7675) [INFO] Cleaning up list of fastest mirrors * 2024-11-07 22:13:57 (7675) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-07 22:13:57 (7692) [INFO] * 2024-11-07 22:13: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-11-07 22:13: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-11-07 22:13:59 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-07 22:14:00 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NqIElKbe5d/ea_profile.json * 2024-11-07 22:14:01 (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/NqIElKbe5d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799. * 2024-11-07 22:14:01 (452) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-08 22:13:44 (8998) [INFO] Self-update of script version 56 requested. * 2024-11-08 22:13:44 (9003) [INFO] Newer version of script found. Downloading. * 2024-11-08 22:13:45 (9012) [INFO] Script update to version 57 successful. * 2024-11-08 22:13:46 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-08 22:13:46 (8441) [INFO] * 2024-11-08 22:13:49 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-08 22:13:49 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-08 22:13:49 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-08 22:13:49 (8441) [INFO] * 2024-11-08 22:14:09 (8454) [INFO] promote_db.apps * 2024-11-08 22:14:09 (8454) [INFO] warning : 7 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] promote_db.campaigns * 2024-11-08 22:14:09 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] promote_db.links * 2024-11-08 22:14:09 (8454) [INFO] warning : 30 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] promote_db.login * 2024-11-08 22:14:09 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] promote_db.queue * 2024-11-08 22:14:09 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] promote_db.subscribers * 2024-11-08 22:14:09 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] trsclix_db.logs * 2024-11-08 22:14:09 (8454) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] trsclix_db.tour_details * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] trsclix_db.tours * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_10_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_11_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 9 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_12_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 101 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_12_postmeta * 2024-11-08 22:14:09 (8454) [INFO] warning : 90 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_12_posts * 2024-11-08 22:14:09 (8454) [INFO] warning : 93 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_12_term_relationships * 2024-11-08 22:14:09 (8454) [INFO] warning : 85 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-08 22:14:09 (8454) [INFO] warning : 93 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_14_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_16_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 12 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_17_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 23 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_21_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 28 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_21_postmeta * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_21_posts * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_23_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_25_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 38 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_27_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_31_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 9 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_32_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 15 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_33_options * 2024-11-08 22:14:09 (8454) [INFO] warning : Table is marked as crashed * 2024-11-08 22:14:09 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-08 22:14:09 (8454) [INFO] error : Corrupt * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_33_postmeta * 2024-11-08 22:14:09 (8454) [INFO] warning : 16 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_33_posts * 2024-11-08 22:14:09 (8454) [INFO] warning : 37 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_comments * 2024-11-08 22:14:09 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 99 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_postmeta * 2024-11-08 22:14:09 (8454) [INFO] warning : 14 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_posts * 2024-11-08 22:14:09 (8454) [INFO] warning : 15 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_term_relationships * 2024-11-08 22:14:09 (8454) [INFO] warning : 13 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_35_term_taxonomy * 2024-11-08 22:14:09 (8454) [INFO] warning : 14 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_36_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 25 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_37_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 37 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-08 22:14:09 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-08 22:14:09 (8454) [INFO] error : Corrupt * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_38_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 13 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_39_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 20 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_3_options * 2024-11-08 22:14:09 (8454) [INFO] warning : 59 clients are using or haven't closed the table properly * 2024-11-08 22:14:09 (8454) [INFO] websites_wp.rs_40_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_41_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 21 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_43_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 20 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_44_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 56 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_44_postmeta * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_45_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 13 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_46_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 20 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_47_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_47_redirection_404 * 2024-11-08 22:14:11 (8454) [INFO] warning : 22 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_47_redirection_items * 2024-11-08 22:14:11 (8454) [INFO] warning : 13 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_47_redirection_logs * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_48_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 51 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_49_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 18 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_52_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 22 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_53_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 19 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_54_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 91 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_55_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 16 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_56_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 29 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_57_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 29 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_58_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 9 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_59_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 23 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_5_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 101 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_61_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_62_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 27 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_63_et_divi_ab_testing_stats * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_63_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 56 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_63_postmeta * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_64_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 30 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_68_comments * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_68_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 98 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_6_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 8 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_7_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_9_comments * 2024-11-08 22:14:11 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_9_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 97 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_blogs * 2024-11-08 22:14:11 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_comments * 2024-11-08 22:14:11 (8454) [INFO] warning : 18 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_options * 2024-11-08 22:14:11 (8454) [INFO] warning : 109 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_posts * 2024-11-08 22:14:11 (8454) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_pro_sites_daily_stats * 2024-11-08 22:14:11 (8454) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_sitemeta * 2024-11-08 22:14:11 (8454) [INFO] warning : 106 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_usermeta * 2024-11-08 22:14:11 (8454) [INFO] warning : 59 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfblockediplog * 2024-11-08 22:14:11 (8454) [INFO] warning : 104 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfblocks7 * 2024-11-08 22:14:11 (8454) [INFO] warning : 103 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfconfig * 2024-11-08 22:14:11 (8454) [INFO] warning : 104 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfcrawlers * 2024-11-08 22:14:11 (8454) [INFO] warning : 86 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfhits * 2024-11-08 22:14:11 (8454) [INFO] warning : 114 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfissues * 2024-11-08 22:14:11 (8454) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-08 22:14:11 (8454) [INFO] warning : 102 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wflocs * 2024-11-08 22:14:11 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wflogins * 2024-11-08 22:14:11 (8454) [INFO] warning : 50 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfnotifications * 2024-11-08 22:14:11 (8454) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfreversecache * 2024-11-08 22:14:11 (8454) [INFO] warning : 51 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfsnipcache * 2024-11-08 22:14:11 (8454) [INFO] warning : 103 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8454) [INFO] websites_wp.rs_wfstatus * 2024-11-08 22:14:11 (8454) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-08 22:14:11 (8471) [INFO] * 2024-11-08 22:14:11 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.apps warning : 7 clients are using or haven't closed the table properly promote_db.campaigns warning : 36 clients are using or haven't closed the table properly promote_db.links warning : 30 clients are using or haven't closed the table properly promote_db.login warning : 2 clients are using or haven't closed the table properly promote_db.queue warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 36 clients are using or haven't closed the table properly trsclix_db.logs warning : 6 clients are using or haven't closed the table properly trsclix_db.tour_details warning : 1 client is using or hasn't closed the table properly trsclix_db.tours warning : 1 client is using or hasn't closed the table properly websites_wp.rs_10_options warning : 5 clients are using or haven't closed the table properly websites_wp.rs_11_options warning : 9 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 101 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 90 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 93 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 85 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 93 clients are using or haven't closed the table properly websites_wp.rs_14_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_16_options warning : 12 clients are using or haven't closed the table properly websites_wp.rs_17_options warning : 23 clients are using or haven't closed the table properly websites_wp.rs_21_options warning : 28 clients are using or haven't closed the table properly websites_wp.rs_21_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_21_posts warning : 1 client is using or hasn't closed the table properly websites_wp.rs_23_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_25_options warning : 38 clients are using or haven't closed the table properly websites_wp.rs_27_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_31_options warning : 9 clients are using or haven't closed the table properly websites_wp.rs_32_options warning : 15 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_33_postmeta warning : 16 clients are using or haven't closed the table properly websites_wp.rs_33_posts warning : 37 clients are using or haven't closed the table properly websites_wp.rs_35_comments warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_options warning : 99 clients are using or haven't closed the table properly websites_wp.rs_35_postmeta warning : 14 clients are using or haven't closed the table properly websites_wp.rs_35_posts warning : 15 clients are using or haven't closed the table properly websites_wp.rs_35_term_relationships warning : 13 clients are using or haven't closed the table properly websites_wp.rs_35_term_taxonomy warning : 14 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 25 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : 37 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_38_options warning : 13 clients are using or haven't closed the table properly websites_wp.rs_39_options warning : 20 clients are using or haven't closed the table properly websites_wp.rs_3_options warning : 59 clients are using or haven't closed the table properly websites_wp.rs_40_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_41_options warning : 21 clients are using or haven't closed the table properly websites_wp.rs_43_options warning : 20 clients are using or haven't closed the table properly websites_wp.rs_44_options warning : 56 clients are using or haven't closed the table properly websites_wp.rs_44_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_45_options warning : 13 clients are using or haven't closed the table properly websites_wp.rs_46_options warning : 20 clients are using or haven't closed the table properly websites_wp.rs_47_options warning : 36 clients are using or haven't closed the table properly websites_wp.rs_47_redirection_404 warning : 22 clients are using or haven't closed the table properly websites_wp.rs_47_redirection_items warning : 13 clients are using or haven't closed the table properly websites_wp.rs_47_redirection_logs warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 51 clients are using or haven't closed the table properly websites_wp.rs_49_options warning : 18 clients are using or haven't closed the table properly websites_wp.rs_52_options warning : 22 clients are using or haven't closed the table properly websites_wp.rs_53_options warning : 19 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 91 clients are using or haven't closed the table properly websites_wp.rs_55_options warning : 16 clients are using or haven't closed the table properly websites_wp.rs_56_options warning : 29 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 29 clients are using or haven't closed the table properly websites_wp.rs_58_options warning : 9 clients are using or haven't closed the table properly websites_wp.rs_59_options warning : 23 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 101 clients are using or haven't closed the table properly websites_wp.rs_61_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_62_options warning : 27 clients are using or haven't closed the table properly websites_wp.rs_63_et_divi_ab_testing_stats warning : 1 client is using or hasn't closed the table properly websites_wp.rs_63_options warning : 56 clients are using or haven't closed the table properly websites_wp.rs_63_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_64_options warning : 30 clients are using or haven't closed the table properly websites_wp.rs_68_comments warning : 1 client is using or hasn't closed the table properly websites_wp.rs_68_options warning : 98 clients are using or haven't closed the table properly websites_wp.rs_6_options warning : 8 clients are using or haven't closed the table properly websites_wp.rs_7_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_9_comments warning : 4 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 97 clients are using or haven't closed the table properly websites_wp.rs_blogs warning : 3 clients are using or haven't closed the table properly websites_wp.rs_comments warning : 18 clients are using or haven't closed the table properly websites_wp.rs_options warning : 109 clients are using or haven't closed the table properly websites_wp.rs_posts warning : 6 clients are using or haven't closed the table properly websites_wp.rs_pro_sites_daily_stats warning : 5 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 106 clients are using or haven't closed the table properly websites_wp.rs_usermeta warning : 59 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 104 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 103 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 104 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 86 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 114 clients are using or haven't closed the table properly websites_wp.rs_wfissues warning : 5 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 102 clients are using or haven't closed the table properly websites_wp.rs_wflocs warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wflogins warning : 50 clients are using or haven't closed the table properly websites_wp.rs_wfnotifications warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfreversecache warning : 51 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 103 clients are using or haven't closed the table properly websites_wp.rs_wfstatus warning : 6 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-08 22:14:11 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-08 22:14:11 (8441) [INFO] * 2024-11-08 22:14:16 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-08 22:14:16 (8441) [INFO] * 2024-11-08 22:14:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 22:14:16 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-08 22:14:17 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-08 22:14:17 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-08 22:14:17 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-08 22:14:17 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-08 22:14:17 (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 22:14:17 (8454) [INFO] Trying other mirror. * 2024-11-08 22:14:17 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-08 22:14:17 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-08 22:14:17 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-08 22:14:17 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-08 22:14:17 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-08 22:14:17 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-08 22:14:17 (8454) [INFO] yum --disablerepo=base ... * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-08 22:14:17 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-08 22:14:17 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] yum-config-manager --disable base * 2024-11-08 22:14:17 (8454) [INFO] or * 2024-11-08 22:14:17 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-08 22:14:17 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-08 22:14:17 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-08 22:14:17 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-08 22:14:17 (8454) [INFO] compromise: * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-08 22:14:17 (8454) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-08 22:14:17 (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 22:14:17 (8471) [INFO] * 2024-11-08 22:14:17 (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 22:14:17 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-08 22:14:17 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-08 22:14:17 (8441) [INFO] * 2024-11-08 22:14:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 22:14:17 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-08 22:14:17 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-08 22:14:17 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-08 22:14:17 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-08 22:14:17 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-08 22:14:17 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-08 22:14:17 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-08 22:14:17 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-08 22:14:17 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-08 22:14:17 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-08 22:14:17 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-08 22:14:18 (8471) [INFO] * 2024-11-08 22:14:18 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-08 22:14:18 (8441) [INFO] * 2024-11-08 22:14:18 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-08 22:14:18 (8454) [INFO] Determining fastest mirrors * 2024-11-08 22:14:20 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-08 22:14:20 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-08 22:14:20 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-08 22:14:20 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-08 22:14:20 (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 22:14:20 (8454) [INFO] Trying other mirror. * 2024-11-08 22:14:20 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-08 22:14:20 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-08 22:14:20 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-08 22:14:20 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-08 22:14:20 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-08 22:14:20 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-08 22:14:20 (8454) [INFO] yum --disablerepo=base ... * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-08 22:14:20 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-08 22:14:20 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] yum-config-manager --disable base * 2024-11-08 22:14:20 (8454) [INFO] or * 2024-11-08 22:14:20 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-08 22:14:20 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-08 22:14:20 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-08 22:14:20 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-08 22:14:20 (8454) [INFO] compromise: * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-08 22:14:20 (8454) [INFO] * 2024-11-08 22:14:20 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-08 22:14:20 (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 22:14:21 (8471) [INFO] * 2024-11-08 22:14:21 (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 22:14:21 (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 22:14:21 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-08 22:14:22 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lFDGuc4zQM/ea_profile.json * 2024-11-08 22:14:23 (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/lFDGuc4zQM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-08 22:14:23 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-09 22:14:34 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-09 22:14:35 (9513) [INFO] Script is up to date. * 2024-11-09 22:14:36 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-09 22:14:36 (8441) [INFO] * 2024-11-09 22:17:25 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-09 22:17:25 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-09 22:17:25 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-09 22:17:25 (8441) [INFO] * 2024-11-09 22:17:45 (8454) [INFO] websites_wp.rs_33_options * 2024-11-09 22:17:45 (8454) [INFO] warning : Table is marked as crashed * 2024-11-09 22:17:45 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-09 22:17:45 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-09 22:17:45 (8454) [INFO] error : Corrupt * 2024-11-09 22:17:45 (8454) [INFO] websites_wp.rs_37_options * 2024-11-09 22:17:45 (8454) [INFO] warning : Table is marked as crashed * 2024-11-09 22:17:45 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-09 22:17:45 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-09 22:17:45 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-09 22:17:45 (8454) [INFO] error : Corrupt * 2024-11-09 22:17:45 (8471) [INFO] * 2024-11-09 22:17:45 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-09 22:17:45 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-09 22:17:45 (8441) [INFO] * 2024-11-09 22:17:49 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-09 22:17:49 (8441) [INFO] * 2024-11-09 22:17:50 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-09 22:17:50 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-09 22:17:51 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-09 22:17:51 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-09 22:17:51 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-09 22:17:51 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-09 22:17:51 (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 22:17:51 (8454) [INFO] Trying other mirror. * 2024-11-09 22:17:51 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-09 22:17:51 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-09 22:17:51 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-09 22:17:51 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-09 22:17:51 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-09 22:17:51 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-09 22:17:51 (8454) [INFO] yum --disablerepo=base ... * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-09 22:17:51 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-09 22:17:51 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] yum-config-manager --disable base * 2024-11-09 22:17:51 (8454) [INFO] or * 2024-11-09 22:17:51 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-09 22:17:51 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-09 22:17:51 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-09 22:17:51 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-09 22:17:51 (8454) [INFO] compromise: * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-09 22:17:51 (8454) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-09 22:17:51 (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 22:17:51 (8471) [INFO] * 2024-11-09 22:17:51 (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 22:17:51 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-09 22:17:51 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-09 22:17:51 (8441) [INFO] * 2024-11-09 22:17:51 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-09 22:17:51 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-09 22:17:51 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-09 22:17:51 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-09 22:17:51 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-09 22:17:51 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-09 22:17:51 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-09 22:17:51 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-09 22:17:51 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-09 22:17:51 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-09 22:17:51 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-09 22:17:51 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-09 22:17:52 (8471) [INFO] * 2024-11-09 22:17:52 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-09 22:17:52 (8441) [INFO] * 2024-11-09 22:17:52 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-09 22:17:52 (8454) [INFO] Determining fastest mirrors * 2024-11-09 22:17:54 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-09 22:17:54 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-09 22:17:54 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-09 22:17:54 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-09 22:17: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-09 22:17:54 (8454) [INFO] Trying other mirror. * 2024-11-09 22:17:54 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-09 22:17:54 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-09 22:17:54 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-09 22:17:54 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-09 22:17:54 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-09 22:17:54 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-09 22:17:54 (8454) [INFO] yum --disablerepo=base ... * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-09 22:17:54 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-09 22:17:54 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] yum-config-manager --disable base * 2024-11-09 22:17:54 (8454) [INFO] or * 2024-11-09 22:17:54 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-09 22:17:54 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-09 22:17:54 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-09 22:17:54 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-09 22:17:54 (8454) [INFO] compromise: * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-09 22:17:54 (8454) [INFO] * 2024-11-09 22:17:54 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-09 22:17: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-09 22:17:54 (8471) [INFO] * 2024-11-09 22:17: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-09 22:17: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-09 22:17:54 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-09 22:17:55 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8gpZbTD7eJ/ea_profile.json * 2024-11-09 22:17: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/8gpZbTD7eJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-09 22:17:57 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-10 22:14:35 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-10 22:14:35 (9513) [INFO] Script is up to date. * 2024-11-10 22:14:37 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-10 22:14:37 (8441) [INFO] * 2024-11-10 22:14:40 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-10 22:14:40 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-10 22:14:40 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-10 22:14:40 (8441) [INFO] * 2024-11-10 22:15:05 (8454) [INFO] websites_wp.rs_33_options * 2024-11-10 22:15:05 (8454) [INFO] warning : Table is marked as crashed * 2024-11-10 22:15:05 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-10 22:15:05 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-10 22:15:05 (8454) [INFO] error : Corrupt * 2024-11-10 22:15:05 (8454) [INFO] websites_wp.rs_37_options * 2024-11-10 22:15:05 (8454) [INFO] warning : Table is marked as crashed * 2024-11-10 22:15:05 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-10 22:15:05 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-10 22:15:05 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-10 22:15:05 (8454) [INFO] error : Corrupt * 2024-11-10 22:15:05 (8471) [INFO] * 2024-11-10 22:15:05 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-10 22:15:05 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-10 22:15:05 (8441) [INFO] * 2024-11-10 22:15:17 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-10 22:15:17 (8441) [INFO] * 2024-11-10 22:15:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 22:15:17 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-10 22:15:21 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-10 22:15:21 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-10 22:15:21 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-10 22:15:21 (8454) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-11-10 22:15:21 (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 22:15:21 (8454) [INFO] Trying other mirror. * 2024-11-10 22:15:21 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-10 22:15:21 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-10 22:15:21 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-10 22:15:21 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-10 22:15:21 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-10 22:15:21 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-10 22:15:21 (8454) [INFO] yum --disablerepo=base ... * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-10 22:15:21 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-10 22:15:21 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] yum-config-manager --disable base * 2024-11-10 22:15:21 (8454) [INFO] or * 2024-11-10 22:15:21 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-10 22:15:21 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-10 22:15:21 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-10 22:15:21 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-10 22:15:21 (8454) [INFO] compromise: * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-10 22:15:21 (8454) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-10 22:15:21 (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 22:15:21 (8471) [INFO] * 2024-11-10 22:15:21 (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 22:15:21 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-10 22:15:21 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-10 22:15:21 (8441) [INFO] * 2024-11-10 22:15:21 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 22:15:21 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-10 22:15:21 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-10 22:15:21 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-10 22:15:21 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-10 22:15:21 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-10 22:15:21 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-10 22:15:21 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-10 22:15:21 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-10 22:15:21 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-10 22:15:21 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-10 22:15:21 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-10 22:15:21 (8471) [INFO] * 2024-11-10 22:15:21 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-10 22:15:21 (8441) [INFO] * 2024-11-10 22:15:22 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-10 22:15:22 (8454) [INFO] Determining fastest mirrors * 2024-11-10 22:15:33 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-10 22:15:33 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-10 22:15:33 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-10 22:15:33 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-10 22:15: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 22:15:33 (8454) [INFO] Trying other mirror. * 2024-11-10 22:15:33 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-10 22:15:33 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-10 22:15:33 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-10 22:15:33 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-10 22:15:33 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-10 22:15:33 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-10 22:15:33 (8454) [INFO] yum --disablerepo=base ... * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-10 22:15:33 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-10 22:15:33 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] yum-config-manager --disable base * 2024-11-10 22:15:33 (8454) [INFO] or * 2024-11-10 22:15:33 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-10 22:15:33 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-10 22:15:33 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-10 22:15:33 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-10 22:15:33 (8454) [INFO] compromise: * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-10 22:15:33 (8454) [INFO] * 2024-11-10 22:15:33 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-10 22:15: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 22:15:33 (8471) [INFO] * 2024-11-10 22:15: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 22:15: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 22:15:34 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-10 22:15:35 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N51ICv4JGD/ea_profile.json * 2024-11-10 22:15:45 (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/N51ICv4JGD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-10 22:15:45 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-11 22:13:42 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-11 22:13:42 (9513) [INFO] Script is up to date. * 2024-11-11 22:13:43 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-11 22:13:43 (8441) [INFO] * 2024-11-11 22:13:46 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-11 22:13:46 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-11 22:13:46 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-11 22:13:46 (8441) [INFO] * 2024-11-11 22:14:11 (8454) [INFO] websites_wp.rs_33_options * 2024-11-11 22:14:11 (8454) [INFO] warning : Table is marked as crashed * 2024-11-11 22:14:11 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-11 22:14:11 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-11 22:14:11 (8454) [INFO] error : Corrupt * 2024-11-11 22:14:11 (8454) [INFO] websites_wp.rs_37_options * 2024-11-11 22:14:11 (8454) [INFO] warning : Table is marked as crashed * 2024-11-11 22:14:11 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-11 22:14:11 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-11 22:14:11 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-11 22:14:11 (8454) [INFO] error : Corrupt * 2024-11-11 22:14:11 (8471) [INFO] * 2024-11-11 22:14:11 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-11 22:14:11 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-11 22:14:11 (8441) [INFO] * 2024-11-11 22:14:15 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-11 22:14:15 (8441) [INFO] * 2024-11-11 22:14:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 22:14:15 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-11 22:14:16 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-11 22:14:16 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-11 22:14:16 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-11 22:14:16 (8454) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-11-11 22:14:17 (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 22:14:17 (8454) [INFO] Trying other mirror. * 2024-11-11 22:14:17 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-11 22:14:17 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-11 22:14:17 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-11 22:14:17 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-11 22:14:17 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-11 22:14:17 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-11 22:14:17 (8454) [INFO] yum --disablerepo=base ... * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-11 22:14:17 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-11 22:14:17 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] yum-config-manager --disable base * 2024-11-11 22:14:17 (8454) [INFO] or * 2024-11-11 22:14:17 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-11 22:14:17 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-11 22:14:17 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-11 22:14:17 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-11 22:14:17 (8454) [INFO] compromise: * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-11 22:14:17 (8454) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-11 22:14:17 (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 22:14:17 (8471) [INFO] * 2024-11-11 22:14:17 (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 22:14:17 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-11 22:14:17 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-11 22:14:17 (8441) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 22:14:17 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-11 22:14:17 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-11 22:14:17 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-11 22:14:17 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-11 22:14:17 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-11 22:14:17 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-11 22:14:17 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-11 22:14:17 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-11 22:14:17 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-11 22:14:17 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-11 22:14:17 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-11 22:14:17 (8471) [INFO] * 2024-11-11 22:14:17 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-11 22:14:17 (8441) [INFO] * 2024-11-11 22:14:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-11 22:14:17 (8454) [INFO] Determining fastest mirrors * 2024-11-11 22:14:21 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-11 22:14:21 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-11 22:14:21 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-11 22:14:21 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-11 22:14:21 (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 22:14:21 (8454) [INFO] Trying other mirror. * 2024-11-11 22:14:21 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-11 22:14:21 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-11 22:14:21 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-11 22:14:21 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-11 22:14:21 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-11 22:14:21 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-11 22:14:21 (8454) [INFO] yum --disablerepo=base ... * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-11 22:14:21 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-11 22:14:21 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] yum-config-manager --disable base * 2024-11-11 22:14:21 (8454) [INFO] or * 2024-11-11 22:14:21 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-11 22:14:21 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-11 22:14:21 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-11 22:14:21 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-11 22:14:21 (8454) [INFO] compromise: * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-11 22:14:21 (8454) [INFO] * 2024-11-11 22:14:21 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-11 22:14:21 (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 22:14:21 (8471) [INFO] * 2024-11-11 22:14:21 (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 22:14:21 (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 22:14:22 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-11 22:14:23 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Ed_MvvmDf/ea_profile.json * 2024-11-11 22:14:24 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4Ed_MvvmDf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-11 22:14:24 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-12 22:13:47 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-12 22:13:47 (9513) [INFO] Script is up to date. * 2024-11-12 22:13:48 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-12 22:13:48 (8441) [INFO] * 2024-11-12 22:13:51 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-12 22:13:51 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-12 22:13:51 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-12 22:13:51 (8441) [INFO] * 2024-11-12 22:14:13 (8454) [INFO] websites_wp.rs_33_options * 2024-11-12 22:14:13 (8454) [INFO] warning : Table is marked as crashed * 2024-11-12 22:14:13 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-12 22:14:13 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-12 22:14:13 (8454) [INFO] error : Corrupt * 2024-11-12 22:14:13 (8454) [INFO] websites_wp.rs_37_options * 2024-11-12 22:14:13 (8454) [INFO] warning : Table is marked as crashed * 2024-11-12 22:14:13 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-12 22:14:13 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-12 22:14:13 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-12 22:14:13 (8454) [INFO] error : Corrupt * 2024-11-12 22:14:13 (8471) [INFO] * 2024-11-12 22:14:13 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-12 22:14:13 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-12 22:14:13 (8441) [INFO] * 2024-11-12 22:14:16 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-12 22:14:16 (8441) [INFO] * 2024-11-12 22:14:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-12 22:14:17 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-12 22:14:17 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-12 22:14:17 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-12 22:14:17 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-12 22:14:17 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-12 22:14:17 (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 22:14:17 (8454) [INFO] Trying other mirror. * 2024-11-12 22:14:17 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-12 22:14:17 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-12 22:14:17 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-12 22:14:17 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-12 22:14:17 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-12 22:14:17 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-12 22:14:17 (8454) [INFO] yum --disablerepo=base ... * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-12 22:14:17 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-12 22:14:17 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] yum-config-manager --disable base * 2024-11-12 22:14:17 (8454) [INFO] or * 2024-11-12 22:14:17 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-12 22:14:17 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-12 22:14:17 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-12 22:14:17 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-12 22:14:17 (8454) [INFO] compromise: * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-12 22:14:17 (8454) [INFO] * 2024-11-12 22:14:17 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-12 22:14:17 (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 22:14:18 (8471) [INFO] * 2024-11-12 22:14:18 (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 22:14:18 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-12 22:14:18 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-12 22:14:18 (8441) [INFO] * 2024-11-12 22:14:18 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-12 22:14:18 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-12 22:14:18 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-12 22:14:18 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-12 22:14:18 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-12 22:14:18 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-12 22:14:18 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-12 22:14:18 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-12 22:14:18 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-12 22:14:18 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-12 22:14:18 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-12 22:14:18 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-12 22:14:18 (8471) [INFO] * 2024-11-12 22:14:18 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-12 22:14:18 (8441) [INFO] * 2024-11-12 22:14:18 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-12 22:14:18 (8454) [INFO] Determining fastest mirrors * 2024-11-12 22:14:20 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-12 22:14:20 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-12 22:14:20 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-12 22:14:20 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-12 22:14:20 (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 22:14:20 (8454) [INFO] Trying other mirror. * 2024-11-12 22:14:20 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-12 22:14:20 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-12 22:14:20 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-12 22:14:20 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-12 22:14:20 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-12 22:14:20 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-12 22:14:20 (8454) [INFO] yum --disablerepo=base ... * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-12 22:14:20 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-12 22:14:20 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] yum-config-manager --disable base * 2024-11-12 22:14:20 (8454) [INFO] or * 2024-11-12 22:14:20 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-12 22:14:20 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-12 22:14:20 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-12 22:14:20 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-12 22:14:20 (8454) [INFO] compromise: * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-12 22:14:20 (8454) [INFO] * 2024-11-12 22:14:20 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-12 22:14:20 (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 22:14:20 (8471) [INFO] * 2024-11-12 22:14:20 (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 22:14:20 (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 22:14:20 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-12 22:14:21 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iA_MFdgbuJ/ea_profile.json * 2024-11-12 22:14:22 (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/iA_MFdgbuJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-12 22:14:22 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-13 22:13:49 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-13 22:13:49 (9513) [INFO] Script is up to date. * 2024-11-13 22:13:51 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-13 22:13:51 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-13 22:13:51 (8441) [INFO] * 2024-11-13 22:13:56 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-13 22:13:56 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-13 22:13:56 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-13 22:13:56 (8441) [INFO] * 2024-11-13 22:14:24 (8454) [INFO] promote_db.campaigns * 2024-11-13 22:14:24 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] promote_db.links * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] promote_db.subscribers * 2024-11-13 22:14:24 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_12_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_12_postmeta * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_12_posts * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_12_term_relationships * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_31_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_33_options * 2024-11-13 22:14:24 (8454) [INFO] warning : Table is marked as crashed * 2024-11-13 22:14:24 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-13 22:14:24 (8454) [INFO] error : Corrupt * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_37_options * 2024-11-13 22:14:24 (8454) [INFO] warning : Table is marked as crashed * 2024-11-13 22:14:24 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-13 22:14:24 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-13 22:14:24 (8454) [INFO] error : Corrupt * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_39_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_54_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_57_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_59_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_5_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_68_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_9_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_options * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_sitemeta * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfblockediplog * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfblocks7 * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfconfig * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfcrawlers * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfhits * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8454) [INFO] websites_wp.rs_wfsnipcache * 2024-11-13 22:14:24 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-13 22:14:24 (8471) [INFO] * 2024-11-13 22:14:24 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 3 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_31_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_39_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_59_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-13 22:14:24 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-13 22:14:24 (8441) [INFO] * 2024-11-13 22:14:29 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-13 22:14:29 (8441) [INFO] * 2024-11-13 22:14:29 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 22:14:30 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-13 22:14:30 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-13 22:14:30 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-13 22:14:30 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-13 22:14:30 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-13 22:14: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-13 22:14:30 (8454) [INFO] Trying other mirror. * 2024-11-13 22:14:30 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-13 22:14:30 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-13 22:14:30 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-13 22:14:30 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-13 22:14:30 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-13 22:14:30 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-13 22:14:30 (8454) [INFO] yum --disablerepo=base ... * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-13 22:14:30 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-13 22:14:30 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] yum-config-manager --disable base * 2024-11-13 22:14:30 (8454) [INFO] or * 2024-11-13 22:14:30 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-13 22:14:30 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-13 22:14:30 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-13 22:14:30 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-13 22:14:30 (8454) [INFO] compromise: * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-13 22:14:30 (8454) [INFO] * 2024-11-13 22:14:30 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-13 22:14: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-13 22:14:30 (8471) [INFO] * 2024-11-13 22:14:30 (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-13 22:14:30 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-13 22:14:30 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-13 22:14:30 (8441) [INFO] * 2024-11-13 22:14:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 22:14:31 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-13 22:14:31 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-13 22:14:31 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-13 22:14:31 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-13 22:14:31 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-13 22:14:31 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-13 22:14:31 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-13 22:14:31 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-13 22:14:31 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-13 22:14:31 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-13 22:14:31 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-13 22:14:31 (8471) [INFO] * 2024-11-13 22:14:31 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-13 22:14:31 (8441) [INFO] * 2024-11-13 22:14:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-13 22:14:32 (8454) [INFO] Determining fastest mirrors * 2024-11-13 22:14:33 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-13 22:14:33 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-13 22:14:33 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-13 22:14:33 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-13 22:14: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-13 22:14:33 (8454) [INFO] Trying other mirror. * 2024-11-13 22:14:33 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-13 22:14:33 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-13 22:14:33 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-13 22:14:33 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-13 22:14:33 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-13 22:14:33 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-13 22:14:33 (8454) [INFO] yum --disablerepo=base ... * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-13 22:14:33 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-13 22:14:33 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] yum-config-manager --disable base * 2024-11-13 22:14:33 (8454) [INFO] or * 2024-11-13 22:14:33 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-13 22:14:33 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-13 22:14:33 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-13 22:14:33 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-13 22:14:33 (8454) [INFO] compromise: * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-13 22:14:33 (8454) [INFO] * 2024-11-13 22:14:33 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-13 22:14: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-13 22:14:33 (8471) [INFO] * 2024-11-13 22:14: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-13 22:14: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-13 22:14:33 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-13 22:14:34 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Jic8gZGObZ/ea_profile.json * 2024-11-13 22:14:36 (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/Jic8gZGObZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-13 22:14:36 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-14 22:13:44 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-14 22:13:44 (9513) [INFO] Script is up to date. * 2024-11-14 22:13:45 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-14 22:13:45 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-14 22:13:45 (8441) [INFO] * 2024-11-14 22:13:49 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-14 22:13:49 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-14 22:13:49 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-14 22:13:49 (8441) [INFO] * 2024-11-14 22:14:17 (8454) [INFO] websites_wp.rs_33_options * 2024-11-14 22:14:17 (8454) [INFO] warning : Table is marked as crashed * 2024-11-14 22:14:17 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-14 22:14:17 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-14 22:14:17 (8454) [INFO] error : Corrupt * 2024-11-14 22:14:17 (8454) [INFO] websites_wp.rs_37_options * 2024-11-14 22:14:17 (8454) [INFO] warning : Table is marked as crashed * 2024-11-14 22:14:17 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-14 22:14:17 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-14 22:14:17 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-14 22:14:17 (8454) [INFO] error : Corrupt * 2024-11-14 22:14:17 (8471) [INFO] * 2024-11-14 22:14:17 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-14 22:14:17 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-14 22:14:17 (8441) [INFO] * 2024-11-14 22:14:23 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-14 22:14:23 (8441) [INFO] * 2024-11-14 22:14:23 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-14 22:14:24 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-14 22:14:25 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-14 22:14:25 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-14 22:14:25 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-14 22:14:25 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-14 22:14: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-14 22:14:26 (8454) [INFO] Trying other mirror. * 2024-11-14 22:14:26 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-14 22:14:26 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-14 22:14:26 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-14 22:14:26 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-14 22:14:26 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-14 22:14:26 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-14 22:14:26 (8454) [INFO] yum --disablerepo=base ... * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-14 22:14:26 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-14 22:14:26 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] yum-config-manager --disable base * 2024-11-14 22:14:26 (8454) [INFO] or * 2024-11-14 22:14:26 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-14 22:14:26 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-14 22:14:26 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-14 22:14:26 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-14 22:14:26 (8454) [INFO] compromise: * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-14 22:14:26 (8454) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-14 22:14: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-14 22:14:26 (8471) [INFO] * 2024-11-14 22:14: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-14 22:14:26 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-14 22:14:26 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-14 22:14:26 (8441) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-14 22:14:26 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-14 22:14:26 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-14 22:14:26 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-14 22:14:26 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-14 22:14:26 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-14 22:14:26 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-14 22:14:26 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-14 22:14:26 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-14 22:14:26 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-14 22:14:26 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-14 22:14:26 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-14 22:14:26 (8471) [INFO] * 2024-11-14 22:14:26 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-14 22:14:26 (8441) [INFO] * 2024-11-14 22:14:26 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-14 22:14:26 (8454) [INFO] Determining fastest mirrors * 2024-11-14 22:14:29 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-14 22:14:29 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-14 22:14:29 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-14 22:14:29 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-14 22:14: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-14 22:14:29 (8454) [INFO] Trying other mirror. * 2024-11-14 22:14:29 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-14 22:14:29 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-14 22:14:29 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-14 22:14:29 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-14 22:14:29 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-14 22:14:29 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-14 22:14:29 (8454) [INFO] yum --disablerepo=base ... * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-14 22:14:29 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-14 22:14:29 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] yum-config-manager --disable base * 2024-11-14 22:14:29 (8454) [INFO] or * 2024-11-14 22:14:29 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-14 22:14:29 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-14 22:14:29 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-14 22:14:29 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-14 22:14:29 (8454) [INFO] compromise: * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-14 22:14:29 (8454) [INFO] * 2024-11-14 22:14:29 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-14 22:14: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-14 22:14:29 (8471) [INFO] * 2024-11-14 22:14:29 (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 22:14:29 (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 22:14:29 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-14 22:14:31 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/p3SrirIG93/ea_profile.json * 2024-11-14 22:14: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/p3SrirIG93/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-14 22:14:33 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-15 22:13:43 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-15 22:13:43 (9513) [INFO] Script is up to date. * 2024-11-15 22:13:44 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-15 22:13:44 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-15 22:13:44 (8441) [INFO] * 2024-11-15 22:13:48 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-15 22:13:48 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-15 22:13:48 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-15 22:13:48 (8441) [INFO] * 2024-11-15 22:14:09 (8454) [INFO] websites_wp.rs_33_options * 2024-11-15 22:14:09 (8454) [INFO] warning : Table is marked as crashed * 2024-11-15 22:14:09 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-15 22:14:09 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-15 22:14:09 (8454) [INFO] error : Corrupt * 2024-11-15 22:14:09 (8454) [INFO] websites_wp.rs_37_options * 2024-11-15 22:14:09 (8454) [INFO] warning : Table is marked as crashed * 2024-11-15 22:14:09 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-15 22:14:09 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-15 22:14:09 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-15 22:14:09 (8454) [INFO] error : Corrupt * 2024-11-15 22:14:09 (8471) [INFO] * 2024-11-15 22:14:09 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-15 22:14:09 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-15 22:14:09 (8441) [INFO] * 2024-11-15 22:14:14 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-15 22:14:14 (8441) [INFO] * 2024-11-15 22:14:14 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 22:14:14 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-15 22:14:15 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-15 22:14:15 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-15 22:14:15 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-15 22:14:15 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-15 22:14:15 (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 22:14:15 (8454) [INFO] Trying other mirror. * 2024-11-15 22:14:15 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-15 22:14:15 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-15 22:14:15 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-15 22:14:15 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-15 22:14:15 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-15 22:14:15 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-15 22:14:15 (8454) [INFO] yum --disablerepo=base ... * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-15 22:14:15 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-15 22:14:15 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] yum-config-manager --disable base * 2024-11-15 22:14:15 (8454) [INFO] or * 2024-11-15 22:14:15 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-15 22:14:15 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-15 22:14:15 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-15 22:14:15 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-15 22:14:15 (8454) [INFO] compromise: * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-15 22:14:15 (8454) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-15 22:14:15 (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 22:14:15 (8471) [INFO] * 2024-11-15 22:14:15 (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 22:14:15 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-15 22:14:15 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-15 22:14:15 (8441) [INFO] * 2024-11-15 22:14:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 22:14:15 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-15 22:14:15 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-15 22:14:15 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-15 22:14:15 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-15 22:14:15 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-15 22:14:15 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-15 22:14:15 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-15 22:14:15 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-15 22:14:15 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-15 22:14:15 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-15 22:14:15 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-15 22:14:15 (8471) [INFO] * 2024-11-15 22:14:15 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-15 22:14:15 (8441) [INFO] * 2024-11-15 22:14:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-15 22:14:16 (8454) [INFO] Determining fastest mirrors * 2024-11-15 22:14:17 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-15 22:14:17 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-15 22:14:17 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-15 22:14:17 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-15 22:14:17 (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 22:14:17 (8454) [INFO] Trying other mirror. * 2024-11-15 22:14:17 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-15 22:14:17 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-15 22:14:17 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-15 22:14:17 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-15 22:14:17 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-15 22:14:17 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-15 22:14:17 (8454) [INFO] yum --disablerepo=base ... * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-15 22:14:17 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-15 22:14:17 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] yum-config-manager --disable base * 2024-11-15 22:14:17 (8454) [INFO] or * 2024-11-15 22:14:17 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-15 22:14:17 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-15 22:14:17 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-15 22:14:17 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-15 22:14:17 (8454) [INFO] compromise: * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-15 22:14:17 (8454) [INFO] * 2024-11-15 22:14:17 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-15 22:14:17 (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 22:14:17 (8471) [INFO] * 2024-11-15 22:14:17 (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 22:14:17 (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 22:14:18 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-15 22:14:19 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/foCfNIs6y2/ea_profile.json * 2024-11-15 22:14:20 (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/foCfNIs6y2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-15 22:14:20 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-16 22:14:35 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-16 22:14:35 (9513) [INFO] Script is up to date. * 2024-11-16 22:14:36 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-16 22:14:36 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-16 22:14:36 (8441) [INFO] * 2024-11-16 22:14:40 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-16 22:14:40 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-16 22:14:40 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-16 22:14:40 (8441) [INFO] * 2024-11-16 22:15:02 (8454) [INFO] promote_db.campaigns * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] promote_db.links * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] promote_db.subscribers * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_12_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_12_postmeta * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_12_posts * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_12_term_relationships * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_25_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_33_options * 2024-11-16 22:15:02 (8454) [INFO] warning : Table is marked as crashed * 2024-11-16 22:15:02 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-16 22:15:02 (8454) [INFO] error : Corrupt * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_35_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_36_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_37_options * 2024-11-16 22:15:02 (8454) [INFO] warning : Table is marked as crashed * 2024-11-16 22:15:02 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-16 22:15:02 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-16 22:15:02 (8454) [INFO] error : Corrupt * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_39_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_41_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_54_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_5_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_62_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_63_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_64_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_68_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_9_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_options * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_sitemeta * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wfblockediplog * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wfblocks7 * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wfconfig * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wfhits * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8454) [INFO] websites_wp.rs_wfsnipcache * 2024-11-16 22:15:02 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-16 22:15:02 (8471) [INFO] * 2024-11-16 22:15:02 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 2 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_12_posts warning : 1 client is using or hasn't closed the table properly websites_wp.rs_12_term_relationships warning : 1 client is using or hasn't closed the table properly websites_wp.rs_12_term_taxonomy warning : 1 client is using or hasn't closed the table properly websites_wp.rs_25_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_39_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_41_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_62_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_63_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-16 22:15:02 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-16 22:15:02 (8441) [INFO] * 2024-11-16 22:15:13 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-16 22:15:13 (8441) [INFO] * 2024-11-16 22:15:13 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 22:15:13 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-16 22:15:14 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-16 22:15:14 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-16 22:15:14 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-16 22:15:14 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-16 22:15:14 (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 22:15:14 (8454) [INFO] Trying other mirror. * 2024-11-16 22:15:14 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-16 22:15:14 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-16 22:15:14 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-16 22:15:14 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-16 22:15:14 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-16 22:15:14 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-16 22:15:14 (8454) [INFO] yum --disablerepo=base ... * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-16 22:15:14 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-16 22:15:14 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] yum-config-manager --disable base * 2024-11-16 22:15:14 (8454) [INFO] or * 2024-11-16 22:15:14 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-16 22:15:14 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-16 22:15:14 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-16 22:15:14 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-16 22:15:14 (8454) [INFO] compromise: * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-16 22:15:14 (8454) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-16 22:15:14 (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 22:15:14 (8471) [INFO] * 2024-11-16 22:15:14 (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 22:15:14 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-16 22:15:14 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-16 22:15:14 (8441) [INFO] * 2024-11-16 22:15:14 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 22:15:15 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-16 22:15:15 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-16 22:15:15 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-16 22:15:15 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-16 22:15:15 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-16 22:15:15 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-16 22:15:15 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-16 22:15:15 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-16 22:15:15 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-16 22:15:15 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-16 22:15:15 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-16 22:15:15 (8471) [INFO] * 2024-11-16 22:15:15 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-16 22:15:15 (8441) [INFO] * 2024-11-16 22:15:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-16 22:15:15 (8454) [INFO] Determining fastest mirrors * 2024-11-16 22:15:18 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-16 22:15:18 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-16 22:15:18 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-16 22:15:18 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-16 22:15:19 (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 22:15:19 (8454) [INFO] Trying other mirror. * 2024-11-16 22:15:19 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-16 22:15:19 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-16 22:15:19 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-16 22:15:19 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-16 22:15:19 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-16 22:15:19 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-16 22:15:19 (8454) [INFO] yum --disablerepo=base ... * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-16 22:15:19 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-16 22:15:19 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] yum-config-manager --disable base * 2024-11-16 22:15:19 (8454) [INFO] or * 2024-11-16 22:15:19 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-16 22:15:19 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-16 22:15:19 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-16 22:15:19 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-16 22:15:19 (8454) [INFO] compromise: * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-16 22:15:19 (8454) [INFO] * 2024-11-16 22:15:19 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-16 22:15:19 (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 22:15:19 (8471) [INFO] * 2024-11-16 22:15:19 (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 22:15:19 (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 22:15:19 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-16 22:15:20 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eO5oitVIJS/ea_profile.json * 2024-11-16 22:15:24 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eO5oitVIJS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-16 22:15:24 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-17 22:14:36 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-17 22:14:36 (9513) [INFO] Script is up to date. * 2024-11-17 22:14:37 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-17 22:14:37 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-17 22:14:37 (8441) [INFO] * 2024-11-17 22:14:40 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-17 22:14:40 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-17 22:14:40 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-17 22:14:40 (8441) [INFO] * 2024-11-17 22:15:05 (8454) [INFO] websites_wp.rs_33_options * 2024-11-17 22:15:05 (8454) [INFO] warning : Table is marked as crashed * 2024-11-17 22:15:05 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-17 22:15:05 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-17 22:15:05 (8454) [INFO] error : Corrupt * 2024-11-17 22:15:05 (8454) [INFO] websites_wp.rs_37_options * 2024-11-17 22:15:05 (8454) [INFO] warning : Table is marked as crashed * 2024-11-17 22:15:05 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-17 22:15:05 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-17 22:15:05 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-17 22:15:05 (8454) [INFO] error : Corrupt * 2024-11-17 22:15:05 (8471) [INFO] * 2024-11-17 22:15:05 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-17 22:15:05 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-17 22:15:05 (8441) [INFO] * 2024-11-17 22:15:23 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-17 22:15:23 (8441) [INFO] * 2024-11-17 22:15:23 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 22:15:24 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-17 22:15:24 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-17 22:15:24 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-17 22:15:24 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-17 22:15:24 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-17 22:15:24 (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 22:15:24 (8454) [INFO] Trying other mirror. * 2024-11-17 22:15:24 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-17 22:15:24 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-17 22:15:24 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-17 22:15:24 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-17 22:15:24 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-17 22:15:24 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-17 22:15:24 (8454) [INFO] yum --disablerepo=base ... * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-17 22:15:24 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-17 22:15:24 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] yum-config-manager --disable base * 2024-11-17 22:15:24 (8454) [INFO] or * 2024-11-17 22:15:24 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-17 22:15:24 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-17 22:15:24 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-17 22:15:24 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-17 22:15:24 (8454) [INFO] compromise: * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-17 22:15:24 (8454) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-17 22:15:24 (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 22:15:24 (8471) [INFO] * 2024-11-17 22:15:24 (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 22:15:24 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-17 22:15:24 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-17 22:15:24 (8441) [INFO] * 2024-11-17 22:15:24 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 22:15:25 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-17 22:15:25 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-17 22:15:25 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-17 22:15:25 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-17 22:15:25 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-17 22:15:25 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-17 22:15:25 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-17 22:15:25 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-17 22:15:25 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-17 22:15:25 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-17 22:15:25 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-17 22:15:25 (8471) [INFO] * 2024-11-17 22:15:25 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-17 22:15:25 (8441) [INFO] * 2024-11-17 22:15:25 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-17 22:15:25 (8454) [INFO] Determining fastest mirrors * 2024-11-17 22:15:27 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-17 22:15:27 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-17 22:15:27 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-17 22:15:27 (8454) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-17 22:15: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-17 22:15:27 (8454) [INFO] Trying other mirror. * 2024-11-17 22:15:27 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-17 22:15:27 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-17 22:15:27 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-17 22:15:27 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-17 22:15:27 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-17 22:15:27 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-17 22:15:27 (8454) [INFO] yum --disablerepo=base ... * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-17 22:15:27 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-17 22:15:27 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] yum-config-manager --disable base * 2024-11-17 22:15:27 (8454) [INFO] or * 2024-11-17 22:15:27 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-17 22:15:27 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-17 22:15:27 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-17 22:15:27 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-17 22:15:27 (8454) [INFO] compromise: * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-17 22:15:27 (8454) [INFO] * 2024-11-17 22:15:27 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-17 22:15: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-17 22:15:27 (8471) [INFO] * 2024-11-17 22:15:27 (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 22:15:27 (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 22:15:28 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-17 22:15:28 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SIWy0GvO82/ea_profile.json * 2024-11-17 22:15:29 (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/SIWy0GvO82/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-17 22:15:29 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-18 22:13:42 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-18 22:13:42 (9513) [INFO] Script is up to date. * 2024-11-18 22:13:44 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-18 22:13:44 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-18 22:13:44 (8441) [INFO] * 2024-11-18 22:13:47 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-18 22:13:47 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-18 22:13:47 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-18 22:13:47 (8441) [INFO] * 2024-11-18 22:14:10 (8454) [INFO] promote_db.campaigns * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] promote_db.links * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] promote_db.subscribers * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_12_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_12_postmeta * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_12_posts * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_12_term_relationships * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_17_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_25_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_32_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_33_options * 2024-11-18 22:14:10 (8454) [INFO] warning : Table is marked as crashed * 2024-11-18 22:14:10 (8454) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-18 22:14:10 (8454) [INFO] error : Corrupt * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_35_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_35_postmeta * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_35_posts * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_35_term_relationships * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_35_term_taxonomy * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_37_options * 2024-11-18 22:14:10 (8454) [INFO] warning : Table is marked as crashed * 2024-11-18 22:14:10 (8454) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-18 22:14:10 (8454) [INFO] error : Found 1057 keys of 1056 * 2024-11-18 22:14:10 (8454) [INFO] error : Corrupt * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_38_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_39_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_44_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_46_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_48_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_49_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_52_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_54_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_57_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_59_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_5_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_62_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_63_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_64_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_68_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_9_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_options * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_sitemeta * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_usermeta * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfblockediplog * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfblocks7 * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfconfig * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfcrawlers * 2024-11-18 22:14:10 (8454) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfhits * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wflogins * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8454) [INFO] websites_wp.rs_wfsnipcache * 2024-11-18 22:14:10 (8454) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-18 22:14:10 (8471) [INFO] * 2024-11-18 22:14:10 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 4 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 3 clients are using or haven't closed the table properly websites_wp.rs_17_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_25_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_32_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_35_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_posts warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_relationships warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_taxonomy warning : 1 client is using or hasn't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_38_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_39_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_44_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_46_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_49_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_52_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_54_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_59_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_62_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_64_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 4 clients are using or haven't closed the table properly websites_wp.rs_usermeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfblockediplog warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfhits warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 4 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-18 22:14:10 (8440) [INFO] Running: /usr/bin/yum list extras * 2024-11-18 22:14:10 (8441) [INFO] * 2024-11-18 22:14:15 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-18 22:14:15 (8441) [INFO] * 2024-11-18 22:14:15 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 22:14:16 (8454) [INFO] Loading mirror speeds from cached hostfile * 2024-11-18 22:14:17 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-18 22:14:17 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-18 22:14:17 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-18 22:14:17 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-18 22:14:17 (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 22:14:17 (8454) [INFO] Trying other mirror. * 2024-11-18 22:14:17 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-18 22:14:17 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-18 22:14:17 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-18 22:14:17 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-18 22:14:17 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-18 22:14:17 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-18 22:14:17 (8454) [INFO] yum --disablerepo=base ... * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-18 22:14:17 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-18 22:14:17 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] yum-config-manager --disable base * 2024-11-18 22:14:17 (8454) [INFO] or * 2024-11-18 22:14:17 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-18 22:14:17 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-18 22:14:17 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-18 22:14:17 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-18 22:14:17 (8454) [INFO] compromise: * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-18 22:14:17 (8454) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-18 22:14:17 (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 22:14:17 (8471) [INFO] * 2024-11-18 22:14:17 (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 22:14:17 (5508) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-18 22:14:17 (8440) [INFO] Running: /usr/bin/yum clean all * 2024-11-18 22:14:17 (8441) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 22:14:17 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-18 22:14:17 (8454) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-18 22:14:17 (8454) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-18 22:14:17 (8454) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-18 22:14:17 (8454) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-18 22:14:17 (8454) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-18 22:14:17 (8454) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-18 22:14:17 (8454) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-18 22:14:17 (8454) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-18 22:14:17 (8454) [INFO] Cleaning up list of fastest mirrors * 2024-11-18 22:14:17 (8454) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-18 22:14:17 (8471) [INFO] * 2024-11-18 22:14:17 (8440) [INFO] Running: /usr/bin/yum makecache * 2024-11-18 22:14:17 (8441) [INFO] * 2024-11-18 22:14:17 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-18 22:14:17 (8454) [INFO] Determining fastest mirrors * 2024-11-18 22:14:19 (8454) [INFO] * EA4: 185.15.22.168 * 2024-11-18 22:14:19 (8454) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-18 22:14:19 (8454) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-18 22:14:19 (8454) [INFO] * epel: mirrors.hostiserver.com * 2024-11-18 22:14:19 (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 22:14:19 (8454) [INFO] Trying other mirror. * 2024-11-18 22:14:19 (8454) [INFO] To address this issue please refer to the below wiki article * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] https://wiki.centos.org/yum-errors * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-18 22:14:19 (8454) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-18 22:14:19 (8454) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-18 22:14:19 (8454) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-18 22:14:19 (8454) [INFO] distribution release than is supported by the repository (and the * 2024-11-18 22:14:19 (8454) [INFO] packages for the previous distribution release still work). * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-18 22:14:19 (8454) [INFO] yum --disablerepo=base ... * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-18 22:14:19 (8454) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-18 22:14:19 (8454) [INFO] again or use --enablerepo for temporary usage: * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] yum-config-manager --disable base * 2024-11-18 22:14:19 (8454) [INFO] or * 2024-11-18 22:14:19 (8454) [INFO] subscription-manager repos --disable=base * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-18 22:14:19 (8454) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-18 22:14:19 (8454) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-18 22:14:19 (8454) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-18 22:14:19 (8454) [INFO] compromise: * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-18 22:14:19 (8454) [INFO] * 2024-11-18 22:14:19 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-18 22:14:19 (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 22:14:19 (8471) [INFO] * 2024-11-18 22:14:19 (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 22:14:19 (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 22:14:19 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-18 22:14:20 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/V2TGVYIMQV/ea_profile.json * 2024-11-18 22:14:22 (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/V2TGVYIMQV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583. * 2024-11-18 22:14:22 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-19 22:13:43 (9491) [INFO] Self-update of script version 57 requested. * 2024-11-19 22:13:44 (9496) [INFO] Newer version of script found. Downloading. * 2024-11-19 22:13:44 (9505) [INFO] Script update to version 58 successful. * 2024-11-19 22:13:45 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-19 22:13:45 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-19 22:13:45 (8445) [INFO] * 2024-11-19 22:13:48 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-19 22:13:48 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-19 22:13:49 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-19 22:13:49 (8445) [INFO] * 2024-11-19 22:14:18 (8458) [INFO] promote_db.campaigns * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] promote_db.links * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] promote_db.subscribers * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_12_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_17_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_32_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_33_options * 2024-11-19 22:14:18 (8458) [INFO] warning : Table is marked as crashed * 2024-11-19 22:14:18 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-19 22:14:18 (8458) [INFO] error : Corrupt * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_35_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_36_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_37_options * 2024-11-19 22:14:18 (8458) [INFO] warning : Table is marked as crashed * 2024-11-19 22:14:18 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-19 22:14:18 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-19 22:14:18 (8458) [INFO] error : Corrupt * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_38_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_43_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_48_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_54_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_5_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_64_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_68_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_9_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_options * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfreversecache * 2024-11-19 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-19 22:14:18 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-19 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-19 22:14:18 (8475) [INFO] * 2024-11-19 22:14:18 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 2 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_17_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_32_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_38_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_43_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfreversecache warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-19 22:14:18 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-19 22:14:18 (8445) [INFO] * 2024-11-19 22:14:22 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-19 22:14:22 (8445) [INFO] * 2024-11-19 22:14:23 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 22:14:23 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-19 22:14:24 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-19 22:14:24 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-19 22:14:24 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-19 22:14:24 (8458) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-11-19 22:14:24 (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-19 22:14:24 (8458) [INFO] Trying other mirror. * 2024-11-19 22:14:24 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-19 22:14:24 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-19 22:14:24 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-19 22:14:24 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-19 22:14:24 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-19 22:14:24 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-19 22:14:24 (8458) [INFO] yum --disablerepo=base ... * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-19 22:14:24 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-19 22:14:24 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] yum-config-manager --disable base * 2024-11-19 22:14:24 (8458) [INFO] or * 2024-11-19 22:14:24 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-19 22:14:24 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-19 22:14:24 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-19 22:14:24 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-19 22:14:24 (8458) [INFO] compromise: * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-19 22:14:24 (8458) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-19 22:14:24 (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-19 22:14:24 (8475) [INFO] * 2024-11-19 22:14:24 (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-19 22:14:24 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-19 22:14:24 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-19 22:14:24 (8445) [INFO] * 2024-11-19 22:14:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 22:14:24 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-19 22:14:24 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-19 22:14:24 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-19 22:14:24 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-19 22:14:24 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-19 22:14:24 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-19 22:14:24 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-19 22:14:24 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-19 22:14:24 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-19 22:14:24 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-19 22:14:24 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-19 22:14:24 (8475) [INFO] * 2024-11-19 22:14:24 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-19 22:14:24 (8445) [INFO] * 2024-11-19 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-19 22:14:25 (8458) [INFO] Determining fastest mirrors * 2024-11-19 22:14:26 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-19 22:14:26 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-19 22:14:26 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-19 22:14:26 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-19 22:14:26 (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-19 22:14:26 (8458) [INFO] Trying other mirror. * 2024-11-19 22:14:26 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-19 22:14:26 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-19 22:14:26 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-19 22:14:26 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-19 22:14:26 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-19 22:14:26 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-19 22:14:26 (8458) [INFO] yum --disablerepo=base ... * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-19 22:14:26 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-19 22:14:26 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] yum-config-manager --disable base * 2024-11-19 22:14:26 (8458) [INFO] or * 2024-11-19 22:14:26 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-19 22:14:26 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-19 22:14:26 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-19 22:14:26 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-19 22:14:26 (8458) [INFO] compromise: * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-19 22:14:26 (8458) [INFO] * 2024-11-19 22:14:26 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-19 22:14:26 (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-19 22:14:26 (8475) [INFO] * 2024-11-19 22:14:26 (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-19 22:14:26 (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-19 22:14:27 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-19 22:14:28 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ikRUduSkE9/ea_profile.json * 2024-11-19 22:14:29 (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/ikRUduSkE9/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-19 22:14:29 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-20 22:13:46 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-20 22:13:47 (9517) [INFO] Script is up to date. * 2024-11-20 22:13:48 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-20 22:13:48 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-20 22:13:48 (8445) [INFO] * 2024-11-20 22:13:51 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-20 22:13:51 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-20 22:13:51 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-20 22:13:51 (8445) [INFO] * 2024-11-20 22:14:18 (8458) [INFO] promote_db.campaigns * 2024-11-20 22:14:18 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] promote_db.links * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] promote_db.subscribers * 2024-11-20 22:14:18 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_33_options * 2024-11-20 22:14:18 (8458) [INFO] warning : Table is marked as crashed * 2024-11-20 22:14:18 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-20 22:14:18 (8458) [INFO] error : Corrupt * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_37_options * 2024-11-20 22:14:18 (8458) [INFO] warning : Table is marked as crashed * 2024-11-20 22:14:18 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-20 22:14:18 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-20 22:14:18 (8458) [INFO] error : Corrupt * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_43_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_52_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_54_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_63_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_68_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_options * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-20 22:14:18 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-20 22:14:18 (8475) [INFO] * 2024-11-20 22:14:18 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 3 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 3 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_43_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_52_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-20 22:14:18 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-20 22:14:18 (8445) [INFO] * 2024-11-20 22:14:23 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 22:14:23 (8445) [INFO] * 2024-11-20 22:14:23 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 22:14:23 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-20 22:14:24 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-20 22:14:24 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-20 22:14:24 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-20 22:14:24 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-20 22:14:25 (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 22:14:25 (8458) [INFO] Trying other mirror. * 2024-11-20 22:14:25 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-20 22:14:25 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-20 22:14:25 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-20 22:14:25 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-20 22:14:25 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-20 22:14:25 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-20 22:14:25 (8458) [INFO] yum --disablerepo=base ... * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-20 22:14:25 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-20 22:14:25 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] yum-config-manager --disable base * 2024-11-20 22:14:25 (8458) [INFO] or * 2024-11-20 22:14:25 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-20 22:14:25 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-20 22:14:25 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-20 22:14:25 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-20 22:14:25 (8458) [INFO] compromise: * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-20 22:14:25 (8458) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-20 22:14:25 (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 22:14:25 (8475) [INFO] * 2024-11-20 22:14:25 (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 22:14:25 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-20 22:14:25 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-20 22:14:25 (8445) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 22:14:25 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-20 22:14:25 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-20 22:14:25 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-20 22:14:25 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-20 22:14:25 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-20 22:14:25 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-20 22:14:25 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-20 22:14:25 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-20 22:14:25 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-20 22:14:25 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-20 22:14:25 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-20 22:14:25 (8475) [INFO] * 2024-11-20 22:14:25 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-20 22:14:25 (8445) [INFO] * 2024-11-20 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-20 22:14:25 (8458) [INFO] Determining fastest mirrors * 2024-11-20 22:14:27 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-20 22:14:27 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-20 22:14:27 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-20 22:14:27 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-20 22:14:27 (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 22:14:27 (8458) [INFO] Trying other mirror. * 2024-11-20 22:14:27 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-20 22:14:27 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-20 22:14:27 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-20 22:14:27 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-20 22:14:27 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-20 22:14:27 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-20 22:14:27 (8458) [INFO] yum --disablerepo=base ... * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-20 22:14:27 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-20 22:14:27 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] yum-config-manager --disable base * 2024-11-20 22:14:27 (8458) [INFO] or * 2024-11-20 22:14:27 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-20 22:14:27 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-20 22:14:27 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-20 22:14:27 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-20 22:14:27 (8458) [INFO] compromise: * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-20 22:14:27 (8458) [INFO] * 2024-11-20 22:14:27 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-20 22:14:27 (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 22:14:27 (8475) [INFO] * 2024-11-20 22:14:27 (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 22:14:27 (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 22:14:28 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-20 22:14:29 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gb3rw3rC_d/ea_profile.json * 2024-11-20 22:14:30 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gb3rw3rC_d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-20 22:14:30 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-21 00:16:12 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-21 00:16:12 (9517) [INFO] Script is up to date. * 2024-11-21 00:16:13 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-21 00:16:14 (315) [INFO] Successfully verified signature for cpanel (key types: release). * 2024-11-21 00:16:14 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-21 00:16:14 (8445) [INFO] * 2024-11-21 00:16:17 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-21 00:16:17 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-21 00:16:17 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-21 00:16:17 (8445) [INFO] * 2024-11-21 00:16:33 (8458) [INFO] websites_wp.rs_33_options * 2024-11-21 00:16:33 (8458) [INFO] warning : Table is marked as crashed * 2024-11-21 00:16:33 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-21 00:16:33 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-21 00:16:33 (8458) [INFO] error : Corrupt * 2024-11-21 00:16:33 (8458) [INFO] websites_wp.rs_37_options * 2024-11-21 00:16:33 (8458) [INFO] warning : Table is marked as crashed * 2024-11-21 00:16:33 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-21 00:16:33 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-21 00:16:33 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-21 00:16:33 (8458) [INFO] error : Corrupt * 2024-11-21 00:16:33 (8475) [INFO] * 2024-11-21 00:16:33 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-21 00:16:33 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-21 00:16:33 (8445) [INFO] * 2024-11-21 00:16:36 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 00:16:36 (8445) [INFO] * 2024-11-21 00:16:36 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 00:16:36 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-21 00:16:36 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-21 00:16:36 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-21 00:16:36 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-21 00:16:36 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-21 00:16:37 (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 00:16:37 (8458) [INFO] Trying other mirror. * 2024-11-21 00:16:37 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-21 00:16:37 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-21 00:16:37 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-21 00:16:37 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-21 00:16:37 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-21 00:16:37 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-21 00:16:37 (8458) [INFO] yum --disablerepo=base ... * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-21 00:16:37 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-21 00:16:37 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] yum-config-manager --disable base * 2024-11-21 00:16:37 (8458) [INFO] or * 2024-11-21 00:16:37 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-21 00:16:37 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-21 00:16:37 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-21 00:16:37 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-21 00:16:37 (8458) [INFO] compromise: * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-21 00:16:37 (8458) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-21 00:16:37 (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 00:16:37 (8475) [INFO] * 2024-11-21 00:16:37 (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 00:16:37 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-21 00:16:37 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-21 00:16:37 (8445) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 00:16:37 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-21 00:16:37 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-21 00:16:37 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-21 00:16:37 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-21 00:16:37 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-21 00:16:37 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-21 00:16:37 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-21 00:16:37 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-21 00:16:37 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-21 00:16:37 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-21 00:16:37 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-21 00:16:37 (8475) [INFO] * 2024-11-21 00:16:37 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 00:16:37 (8445) [INFO] * 2024-11-21 00:16:37 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 00:16:37 (8458) [INFO] Determining fastest mirrors * 2024-11-21 00:16:38 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-21 00:16:38 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-21 00:16:38 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-21 00:16:38 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-21 00:16: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 00:16:38 (8458) [INFO] Trying other mirror. * 2024-11-21 00:16:38 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-21 00:16:38 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-21 00:16:38 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-21 00:16:38 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-21 00:16:38 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-21 00:16:38 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-21 00:16:38 (8458) [INFO] yum --disablerepo=base ... * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-21 00:16:38 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-21 00:16:38 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] yum-config-manager --disable base * 2024-11-21 00:16:38 (8458) [INFO] or * 2024-11-21 00:16:38 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-21 00:16:38 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-21 00:16:38 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-21 00:16:38 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-21 00:16:38 (8458) [INFO] compromise: * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-21 00:16:38 (8458) [INFO] * 2024-11-21 00:16:38 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-21 00:16: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 00:16:39 (8475) [INFO] * 2024-11-21 00:16:39 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-11-21 00:16:39 (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 00:16:39 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-21 00:16:40 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4cGsYX1CBi/ea_profile.json * 2024-11-21 00:16: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/4cGsYX1CBi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-21 00:16:41 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-21 22:13:41 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-21 22:13:41 (9517) [INFO] Script is up to date. * 2024-11-21 22:13:42 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-21 22:13:42 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-21 22:13:42 (8445) [INFO] * 2024-11-21 22:13:45 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-21 22:13:45 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-21 22:13:45 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-21 22:13:45 (8445) [INFO] * 2024-11-21 22:14:09 (8458) [INFO] promote_db.campaigns * 2024-11-21 22:14:09 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] promote_db.links * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] promote_db.subscribers * 2024-11-21 22:14:09 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_12_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_12_postmeta * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_12_posts * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_12_term_relationships * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_21_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_33_options * 2024-11-21 22:14:09 (8458) [INFO] warning : Table is marked as crashed * 2024-11-21 22:14:09 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-21 22:14:09 (8458) [INFO] error : Corrupt * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_35_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_35_postmeta * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_35_posts * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_35_term_relationships * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_35_term_taxonomy * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_36_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_37_options * 2024-11-21 22:14:09 (8458) [INFO] warning : Table is marked as crashed * 2024-11-21 22:14:09 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-21 22:14:09 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-21 22:14:09 (8458) [INFO] error : Corrupt * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_3_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_43_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_46_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_48_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_54_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_5_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_63_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_68_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_9_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_options * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-21 22:14:09 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-21 22:14:09 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-21 22:14:09 (8475) [INFO] * 2024-11-21 22:14:09 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 3 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_21_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_35_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_35_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_35_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_35_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_3_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_43_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_46_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-21 22:14:09 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-21 22:14:09 (8445) [INFO] * 2024-11-21 22:14:12 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 22:14:12 (8445) [INFO] * 2024-11-21 22:14:13 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 22:14:13 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-21 22:14:13 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-21 22:14:13 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-21 22:14:13 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-21 22:14:13 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-21 22:14:14 (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 22:14:14 (8458) [INFO] Trying other mirror. * 2024-11-21 22:14:14 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-21 22:14:14 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-21 22:14:14 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-21 22:14:14 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-21 22:14:14 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-21 22:14:14 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-21 22:14:14 (8458) [INFO] yum --disablerepo=base ... * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-21 22:14:14 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-21 22:14:14 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] yum-config-manager --disable base * 2024-11-21 22:14:14 (8458) [INFO] or * 2024-11-21 22:14:14 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-21 22:14:14 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-21 22:14:14 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-21 22:14:14 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-21 22:14:14 (8458) [INFO] compromise: * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-21 22:14:14 (8458) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-21 22:14:14 (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 22:14:14 (8475) [INFO] * 2024-11-21 22:14:14 (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 22:14:14 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-21 22:14:14 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-21 22:14:14 (8445) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 22:14:14 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-21 22:14:14 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-21 22:14:14 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-21 22:14:14 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-21 22:14:14 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-21 22:14:14 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-21 22:14:14 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-21 22:14:14 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-21 22:14:14 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-21 22:14:14 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-21 22:14:14 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-21 22:14:14 (8475) [INFO] * 2024-11-21 22:14:14 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-21 22:14:14 (8445) [INFO] * 2024-11-21 22:14:14 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-21 22:14:14 (8458) [INFO] Determining fastest mirrors * 2024-11-21 22:14:16 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-21 22:14:16 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-21 22:14:16 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-21 22:14:16 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-21 22:14:16 (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 22:14:16 (8458) [INFO] Trying other mirror. * 2024-11-21 22:14:16 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-21 22:14:16 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-21 22:14:16 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-21 22:14:16 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-21 22:14:16 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-21 22:14:16 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-21 22:14:16 (8458) [INFO] yum --disablerepo=base ... * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-21 22:14:16 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-21 22:14:16 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] yum-config-manager --disable base * 2024-11-21 22:14:16 (8458) [INFO] or * 2024-11-21 22:14:16 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-21 22:14:16 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-21 22:14:16 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-21 22:14:16 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-21 22:14:16 (8458) [INFO] compromise: * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-21 22:14:16 (8458) [INFO] * 2024-11-21 22:14:16 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-21 22:14:16 (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 22:14:16 (8475) [INFO] * 2024-11-21 22:14:16 (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 22:14:16 (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 22:14:16 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-21 22:14:17 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ldfQHm15Vz/ea_profile.json * 2024-11-21 22:14: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/ldfQHm15Vz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-21 22:14:18 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-22 22:13:44 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-22 22:13:44 (9517) [INFO] Script is up to date. * 2024-11-22 22:13:45 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-22 22:13:45 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-22 22:13:45 (8445) [INFO] * 2024-11-22 22:13:48 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-22 22:13:48 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-22 22:13:48 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-22 22:13:48 (8445) [INFO] * 2024-11-22 22:14:12 (8458) [INFO] promote_db.campaigns * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] promote_db.links * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] promote_db.subscribers * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_12_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_12_postmeta * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_12_posts * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_12_term_relationships * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_25_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_33_options * 2024-11-22 22:14:12 (8458) [INFO] warning : Table is marked as crashed * 2024-11-22 22:14:12 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-22 22:14:12 (8458) [INFO] error : Corrupt * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_35_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_35_postmeta * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_35_posts * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_35_term_relationships * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_35_term_taxonomy * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_36_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_37_options * 2024-11-22 22:14:12 (8458) [INFO] warning : Table is marked as crashed * 2024-11-22 22:14:12 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-22 22:14:12 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-22 22:14:12 (8458) [INFO] error : Corrupt * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_48_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_49_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_54_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_55_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_57_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_5_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_62_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_63_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_64_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_68_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_9_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_options * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_pro_sites_daily_stats * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfnotifications * 2024-11-22 22:14:12 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-22 22:14:12 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-22 22:14:12 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-22 22:14:12 (8475) [INFO] * 2024-11-22 22:14:12 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 2 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_25_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_posts warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_relationships warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_taxonomy warning : 1 client is using or hasn't closed the table properly websites_wp.rs_36_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_48_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_49_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_55_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_57_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_62_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_63_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_pro_sites_daily_stats warning : 1 client is using or hasn't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfnotifications warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-22 22:14:12 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-22 22:14:12 (8445) [INFO] * 2024-11-22 22:14:16 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-22 22:14:16 (8445) [INFO] * 2024-11-22 22:14:16 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 22:14:16 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-22 22:14:17 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-22 22:14:17 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-22 22:14:17 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-22 22:14:17 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-22 22:14:18 (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 22:14:18 (8458) [INFO] Trying other mirror. * 2024-11-22 22:14:18 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-22 22:14:18 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-22 22:14:18 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-22 22:14:18 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-22 22:14:18 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-22 22:14:18 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-22 22:14:18 (8458) [INFO] yum --disablerepo=base ... * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-22 22:14:18 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-22 22:14:18 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] yum-config-manager --disable base * 2024-11-22 22:14:18 (8458) [INFO] or * 2024-11-22 22:14:18 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-22 22:14:18 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-22 22:14:18 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-22 22:14:18 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-22 22:14:18 (8458) [INFO] compromise: * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-22 22:14:18 (8458) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-22 22:14:18 (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 22:14:18 (8475) [INFO] * 2024-11-22 22:14:18 (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 22:14:18 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-22 22:14:18 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-22 22:14:18 (8445) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 22:14:18 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-22 22:14:18 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-22 22:14:18 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-22 22:14:18 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-22 22:14:18 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-22 22:14:18 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-22 22:14:18 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-22 22:14:18 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-22 22:14:18 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-22 22:14:18 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-22 22:14:18 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-22 22:14:18 (8475) [INFO] * 2024-11-22 22:14:18 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-22 22:14:18 (8445) [INFO] * 2024-11-22 22:14:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-22 22:14:18 (8458) [INFO] Determining fastest mirrors * 2024-11-22 22:14:20 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-22 22:14:20 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-22 22:14:20 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-22 22:14:20 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-22 22:14:20 (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 22:14:20 (8458) [INFO] Trying other mirror. * 2024-11-22 22:14:20 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-22 22:14:20 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-22 22:14:20 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-22 22:14:20 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-22 22:14:20 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-22 22:14:20 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-22 22:14:20 (8458) [INFO] yum --disablerepo=base ... * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-22 22:14:20 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-22 22:14:20 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] yum-config-manager --disable base * 2024-11-22 22:14:20 (8458) [INFO] or * 2024-11-22 22:14:20 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-22 22:14:20 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-22 22:14:20 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-22 22:14:20 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-22 22:14:20 (8458) [INFO] compromise: * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-22 22:14:20 (8458) [INFO] * 2024-11-22 22:14:20 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-22 22:14:20 (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 22:14:20 (8475) [INFO] * 2024-11-22 22:14:20 (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 22:14:20 (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 22:14:20 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-22 22:14:21 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5voKwimbXI/ea_profile.json * 2024-11-22 22:14:22 (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/5voKwimbXI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-22 22:14:22 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-23 22:14:33 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-23 22:14:33 (9517) [INFO] Script is up to date. * 2024-11-23 22:14:35 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-23 22:14:35 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-23 22:14:35 (8445) [INFO] * 2024-11-23 22:14:38 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-23 22:14:38 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-23 22:14:38 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-23 22:14:38 (8445) [INFO] * 2024-11-23 22:15:02 (8458) [INFO] promote_db.campaigns * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] promote_db.links * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] promote_db.subscribers * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_12_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_12_postmeta * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_12_posts * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_12_term_relationships * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_32_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_33_options * 2024-11-23 22:15:02 (8458) [INFO] warning : Table is marked as crashed * 2024-11-23 22:15:02 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-23 22:15:02 (8458) [INFO] error : Corrupt * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_35_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_37_options * 2024-11-23 22:15:02 (8458) [INFO] warning : Table is marked as crashed * 2024-11-23 22:15:02 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-23 22:15:02 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-23 22:15:02 (8458) [INFO] error : Corrupt * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_38_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_46_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_47_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_49_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_52_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_55_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_5_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_63_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_64_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_68_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_9_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_options * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-23 22:15:02 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-23 22:15:02 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-23 22:15:02 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-23 22:15:02 (8475) [INFO] * 2024-11-23 22:15:02 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 2 clients are using or haven't closed the table properly promote_db.links warning : 2 clients are using or haven't closed the table properly promote_db.subscribers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_32_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_38_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_46_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_47_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_49_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_52_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_55_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfsnipcache warning : 2 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-23 22:15:02 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-23 22:15:02 (8445) [INFO] * 2024-11-23 22:15:08 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-23 22:15:08 (8445) [INFO] * 2024-11-23 22:15:08 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 22:15:08 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-23 22:15:10 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-23 22:15:10 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-23 22:15:10 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-23 22:15:10 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-23 22:15:10 (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 22:15:10 (8458) [INFO] Trying other mirror. * 2024-11-23 22:15:10 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-23 22:15:10 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-23 22:15:10 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-23 22:15:10 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-23 22:15:10 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-23 22:15:10 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-23 22:15:10 (8458) [INFO] yum --disablerepo=base ... * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-23 22:15:10 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-23 22:15:10 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] yum-config-manager --disable base * 2024-11-23 22:15:10 (8458) [INFO] or * 2024-11-23 22:15:10 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-23 22:15:10 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-23 22:15:10 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-23 22:15:10 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-23 22:15:10 (8458) [INFO] compromise: * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-23 22:15:10 (8458) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-23 22:15:10 (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 22:15:10 (8475) [INFO] * 2024-11-23 22:15:10 (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 22:15:10 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-23 22:15:10 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-23 22:15:10 (8445) [INFO] * 2024-11-23 22:15:10 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 22:15:10 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-23 22:15:10 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-23 22:15:10 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-23 22:15:10 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-23 22:15:10 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-23 22:15:10 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-23 22:15:10 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-23 22:15:10 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-23 22:15:10 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-23 22:15:10 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-23 22:15:10 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-23 22:15:10 (8475) [INFO] * 2024-11-23 22:15:10 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-23 22:15:10 (8445) [INFO] * 2024-11-23 22:15:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-23 22:15:11 (8458) [INFO] Determining fastest mirrors * 2024-11-23 22:15:15 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-23 22:15:15 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-23 22:15:15 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-23 22:15:15 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-23 22:15:15 (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 22:15:15 (8458) [INFO] Trying other mirror. * 2024-11-23 22:15:15 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-23 22:15:15 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-23 22:15:15 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-23 22:15:15 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-23 22:15:15 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-23 22:15:15 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-23 22:15:15 (8458) [INFO] yum --disablerepo=base ... * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-23 22:15:15 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-23 22:15:15 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] yum-config-manager --disable base * 2024-11-23 22:15:15 (8458) [INFO] or * 2024-11-23 22:15:15 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-23 22:15:15 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-23 22:15:15 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-23 22:15:15 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-23 22:15:15 (8458) [INFO] compromise: * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-23 22:15:15 (8458) [INFO] * 2024-11-23 22:15:15 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-23 22:15:15 (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 22:15:15 (8475) [INFO] * 2024-11-23 22:15:15 (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 22:15:15 (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 22:15:15 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-23 22:15:16 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9dc00XtAq0/ea_profile.json * 2024-11-23 22:15: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/9dc00XtAq0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-23 22:15:18 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-24 22:14:38 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-24 22:14:38 (9517) [INFO] Script is up to date. * 2024-11-24 22:14:39 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-24 22:14:39 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-24 22:14:39 (8445) [INFO] * 2024-11-24 22:14:44 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-24 22:14:44 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-24 22:14:44 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-24 22:14:44 (8445) [INFO] * 2024-11-24 22:15:38 (8458) [INFO] websites_wp.rs_33_options * 2024-11-24 22:15:38 (8458) [INFO] warning : Table is marked as crashed * 2024-11-24 22:15:38 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-24 22:15:38 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-24 22:15:38 (8458) [INFO] error : Corrupt * 2024-11-24 22:15:38 (8458) [INFO] websites_wp.rs_37_options * 2024-11-24 22:15:38 (8458) [INFO] warning : Table is marked as crashed * 2024-11-24 22:15:38 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-24 22:15:38 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-24 22:15:38 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-24 22:15:38 (8458) [INFO] error : Corrupt * 2024-11-24 22:15:38 (8475) [INFO] * 2024-11-24 22:15:38 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-24 22:15:38 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-24 22:15:38 (8445) [INFO] * 2024-11-24 22:15:44 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-24 22:15:44 (8445) [INFO] * 2024-11-24 22:15:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 22:15:44 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-24 22:15:46 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-24 22:15:46 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-24 22:15:46 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-24 22:15:46 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-24 22:15: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-24 22:15:46 (8458) [INFO] Trying other mirror. * 2024-11-24 22:15:46 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-24 22:15:46 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-24 22:15:46 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-24 22:15:46 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-24 22:15:46 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-24 22:15:46 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-24 22:15:46 (8458) [INFO] yum --disablerepo=base ... * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-24 22:15:46 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-24 22:15:46 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] yum-config-manager --disable base * 2024-11-24 22:15:46 (8458) [INFO] or * 2024-11-24 22:15:46 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-24 22:15:46 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-24 22:15:46 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-24 22:15:46 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-24 22:15:46 (8458) [INFO] compromise: * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-24 22:15:46 (8458) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-24 22:15: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-24 22:15:46 (8475) [INFO] * 2024-11-24 22:15:46 (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 22:15:46 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-24 22:15:46 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-24 22:15:46 (8445) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 22:15:46 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-24 22:15:46 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-24 22:15:46 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-24 22:15:46 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-24 22:15:46 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-24 22:15:46 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-24 22:15:46 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-24 22:15:46 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-24 22:15:46 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-24 22:15:46 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-24 22:15:46 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-24 22:15:46 (8475) [INFO] * 2024-11-24 22:15:46 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-24 22:15:46 (8445) [INFO] * 2024-11-24 22:15:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-24 22:15:46 (8458) [INFO] Determining fastest mirrors * 2024-11-24 22:15:49 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-24 22:15:49 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-24 22:15:49 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-24 22:15:49 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-24 22:15:50 (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 22:15:50 (8458) [INFO] Trying other mirror. * 2024-11-24 22:15:50 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-24 22:15:50 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-24 22:15:50 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-24 22:15:50 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-24 22:15:50 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-24 22:15:50 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-24 22:15:50 (8458) [INFO] yum --disablerepo=base ... * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-24 22:15:50 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-24 22:15:50 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] yum-config-manager --disable base * 2024-11-24 22:15:50 (8458) [INFO] or * 2024-11-24 22:15:50 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-24 22:15:50 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-24 22:15:50 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-24 22:15:50 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-24 22:15:50 (8458) [INFO] compromise: * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-24 22:15:50 (8458) [INFO] * 2024-11-24 22:15:50 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-24 22:15:50 (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 22:15:50 (8475) [INFO] * 2024-11-24 22:15:50 (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 22:15:50 (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 22:15:50 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-24 22:15:51 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lsmuuPuHIR/ea_profile.json * 2024-11-24 22:15:53 (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/lsmuuPuHIR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-24 22:15:53 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-25 22:13:43 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-25 22:13:44 (9517) [INFO] Script is up to date. * 2024-11-25 22:13:45 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-25 22:13:45 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-25 22:13:45 (8445) [INFO] * 2024-11-25 22:13:48 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-25 22:13:48 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-25 22:13:48 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-25 22:13:48 (8445) [INFO] * 2024-11-25 22:14:13 (8458) [INFO] promote_db.campaigns * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] promote_db.links * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] promote_db.subscribers * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_12_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_33_options * 2024-11-25 22:14:13 (8458) [INFO] warning : Table is marked as crashed * 2024-11-25 22:14:13 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-25 22:14:13 (8458) [INFO] error : Corrupt * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_35_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_36_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_37_options * 2024-11-25 22:14:13 (8458) [INFO] warning : Table is marked as crashed * 2024-11-25 22:14:13 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-25 22:14:13 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-25 22:14:13 (8458) [INFO] error : Corrupt * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_41_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_52_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_54_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_56_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_5_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_68_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_9_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_options * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfreversecache * 2024-11-25 22:14:13 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-25 22:14:13 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-25 22:14:13 (8475) [INFO] * 2024-11-25 22:14:13 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 3 clients are using or haven't closed the table properly promote_db.links warning : 3 clients are using or haven't closed the table properly promote_db.subscribers warning : 3 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_41_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_52_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_56_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_5_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfreversecache warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 3 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-25 22:14:13 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-25 22:14:13 (8445) [INFO] * 2024-11-25 22:14:17 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-25 22:14:17 (8445) [INFO] * 2024-11-25 22:14:18 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 22:14:18 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-25 22:14:19 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-25 22:14:19 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-25 22:14:19 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-25 22:14:19 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-25 22:14:19 (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 22:14:19 (8458) [INFO] Trying other mirror. * 2024-11-25 22:14:19 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-25 22:14:19 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-25 22:14:19 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-25 22:14:19 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-25 22:14:19 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-25 22:14:19 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-25 22:14:19 (8458) [INFO] yum --disablerepo=base ... * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-25 22:14:19 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-25 22:14:19 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] yum-config-manager --disable base * 2024-11-25 22:14:19 (8458) [INFO] or * 2024-11-25 22:14:19 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-25 22:14:19 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-25 22:14:19 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-25 22:14:19 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-25 22:14:19 (8458) [INFO] compromise: * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-25 22:14:19 (8458) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-25 22:14:19 (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 22:14:19 (8475) [INFO] * 2024-11-25 22:14:19 (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 22:14:19 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-25 22:14:19 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-25 22:14:19 (8445) [INFO] * 2024-11-25 22:14:19 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 22:14:20 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-25 22:14:20 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-25 22:14:20 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-25 22:14:20 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-25 22:14:20 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-25 22:14:20 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-25 22:14:20 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-25 22:14:20 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-25 22:14:20 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-25 22:14:20 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-25 22:14:20 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-25 22:14:20 (8475) [INFO] * 2024-11-25 22:14:20 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-25 22:14:20 (8445) [INFO] * 2024-11-25 22:14:20 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-25 22:14:20 (8458) [INFO] Determining fastest mirrors * 2024-11-25 22:14:23 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-25 22:14:23 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-25 22:14:23 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-25 22:14:23 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-25 22:14:23 (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 22:14:23 (8458) [INFO] Trying other mirror. * 2024-11-25 22:14:23 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-25 22:14:23 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-25 22:14:23 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-25 22:14:23 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-25 22:14:23 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-25 22:14:23 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-25 22:14:23 (8458) [INFO] yum --disablerepo=base ... * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-25 22:14:23 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-25 22:14:23 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] yum-config-manager --disable base * 2024-11-25 22:14:23 (8458) [INFO] or * 2024-11-25 22:14:23 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-25 22:14:23 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-25 22:14:23 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-25 22:14:23 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-25 22:14:23 (8458) [INFO] compromise: * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-25 22:14:23 (8458) [INFO] * 2024-11-25 22:14:23 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-25 22:14:23 (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 22:14:23 (8475) [INFO] * 2024-11-25 22:14:23 (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 22:14:23 (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 22:14:23 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-25 22:14:24 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fDfiIUVx1s/ea_profile.json * 2024-11-25 22:14:26 (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/fDfiIUVx1s/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-25 22:14:26 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-26 22:14:25 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-26 22:14:25 (9517) [INFO] Script is up to date. * 2024-11-26 22:14:27 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-26 22:14:27 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-26 22:14:27 (8445) [INFO] * 2024-11-26 22:14:32 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-26 22:14:32 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-26 22:14:32 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-26 22:14:32 (8445) [INFO] * 2024-11-26 22:14:54 (8458) [INFO] promote_db.campaigns * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] promote_db.links * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] promote_db.subscribers * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_11_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_12_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_12_postmeta * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_12_posts * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_12_term_relationships * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_16_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_17_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_21_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_25_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_31_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_32_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_33_options * 2024-11-26 22:14:54 (8458) [INFO] warning : Table is marked as crashed * 2024-11-26 22:14:54 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-26 22:14:54 (8458) [INFO] error : Corrupt * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_35_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_36_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_37_options * 2024-11-26 22:14:54 (8458) [INFO] warning : Table is marked as crashed * 2024-11-26 22:14:54 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-26 22:14:54 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-26 22:14:54 (8458) [INFO] error : Corrupt * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_38_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_39_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_3_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_41_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_43_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_44_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_45_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_46_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_47_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_48_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_49_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_52_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_53_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_54_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_55_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_56_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_57_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_58_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_59_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_5_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_62_options * 2024-11-26 22:14:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:54 (8458) [INFO] websites_wp.rs_63_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_64_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_68_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_6_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_9_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_options * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_pro_sites_daily_stats * 2024-11-26 22:14:55 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-26 22:14:55 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfnotifications * 2024-11-26 22:14:55 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfreversecache * 2024-11-26 22:14:55 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-26 22:14:55 (8458) [INFO] warning : 6 clients are using or haven't closed the table properly * 2024-11-26 22:14:55 (8475) [INFO] * 2024-11-26 22:14:55 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 6 clients are using or haven't closed the table properly promote_db.links warning : 6 clients are using or haven't closed the table properly promote_db.subscribers warning : 6 clients are using or haven't closed the table properly websites_wp.rs_11_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 4 clients are using or haven't closed the table properly websites_wp.rs_16_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_17_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_21_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_25_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_31_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_32_options warning : 5 clients are using or haven't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_36_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_38_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_39_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_3_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_41_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_43_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_44_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_45_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_46_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_47_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 5 clients are using or haven't closed the table properly websites_wp.rs_49_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_52_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_53_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_55_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_56_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_58_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_59_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 5 clients are using or haven't closed the table properly websites_wp.rs_62_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_6_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_9_options warning : 5 clients are using or haven't closed the table properly websites_wp.rs_options warning : 6 clients are using or haven't closed the table properly websites_wp.rs_pro_sites_daily_stats warning : 1 client is using or hasn't closed the table properly websites_wp.rs_sitemeta warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 5 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 6 clients are using or haven't closed the table properly websites_wp.rs_wfnotifications warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfreversecache warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 6 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-26 22:14:55 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-26 22:14:55 (8445) [INFO] * 2024-11-26 22:14:58 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-26 22:14:58 (8445) [INFO] * 2024-11-26 22:14:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 22:14:58 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-26 22:14:59 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-26 22:14:59 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-26 22:14:59 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-26 22:14:59 (8458) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-11-26 22:14: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-26 22:14:59 (8458) [INFO] Trying other mirror. * 2024-11-26 22:14:59 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-26 22:14:59 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-26 22:14:59 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-26 22:14:59 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-26 22:14:59 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-26 22:14:59 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-26 22:14:59 (8458) [INFO] yum --disablerepo=base ... * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-26 22:14:59 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-26 22:14:59 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] yum-config-manager --disable base * 2024-11-26 22:14:59 (8458) [INFO] or * 2024-11-26 22:14:59 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-26 22:14:59 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-26 22:14:59 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-26 22:14:59 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-26 22:14:59 (8458) [INFO] compromise: * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-26 22:14:59 (8458) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-26 22:14: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-26 22:14:59 (8475) [INFO] * 2024-11-26 22:14: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-26 22:14:59 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-26 22:14:59 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-26 22:14:59 (8445) [INFO] * 2024-11-26 22:14:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 22:14:59 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-26 22:14:59 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-26 22:14:59 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-26 22:14:59 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-26 22:14:59 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-26 22:14:59 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-26 22:14:59 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-26 22:14:59 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-26 22:14:59 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-26 22:15:00 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-26 22:15:00 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-26 22:15:00 (8475) [INFO] * 2024-11-26 22:15:00 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-26 22:15:00 (8445) [INFO] * 2024-11-26 22:15:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-26 22:15:00 (8458) [INFO] Determining fastest mirrors * 2024-11-26 22:15:01 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-26 22:15:01 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-26 22:15:01 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-26 22:15:01 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-26 22:15:01 (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 22:15:01 (8458) [INFO] Trying other mirror. * 2024-11-26 22:15:01 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-26 22:15:01 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-26 22:15:01 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-26 22:15:01 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-26 22:15:01 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-26 22:15:01 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-26 22:15:01 (8458) [INFO] yum --disablerepo=base ... * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-26 22:15:01 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-26 22:15:01 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] yum-config-manager --disable base * 2024-11-26 22:15:01 (8458) [INFO] or * 2024-11-26 22:15:01 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-26 22:15:01 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-26 22:15:01 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-26 22:15:01 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-26 22:15:01 (8458) [INFO] compromise: * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-26 22:15:01 (8458) [INFO] * 2024-11-26 22:15:01 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-26 22:15:01 (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 22:15:01 (8475) [INFO] * 2024-11-26 22:15:01 (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 22:15:01 (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 22:15:02 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-26 22:15:03 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lgWwkgxnnq/ea_profile.json * 2024-11-26 22:15:04 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lgWwkgxnnq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-26 22:15:04 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-27 22:13:40 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-27 22:13:40 (9517) [INFO] Script is up to date. * 2024-11-27 22:13:41 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-27 22:13:41 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-27 22:13:41 (8445) [INFO] * 2024-11-27 22:13:44 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-27 22:13:44 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-27 22:13:44 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-27 22:13:44 (8445) [INFO] * 2024-11-27 22:14:07 (8458) [INFO] websites_wp.rs_33_options * 2024-11-27 22:14:07 (8458) [INFO] warning : Table is marked as crashed * 2024-11-27 22:14:07 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-27 22:14:07 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-27 22:14:07 (8458) [INFO] error : Corrupt * 2024-11-27 22:14:07 (8458) [INFO] websites_wp.rs_37_options * 2024-11-27 22:14:07 (8458) [INFO] warning : Table is marked as crashed * 2024-11-27 22:14:07 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-27 22:14:07 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-27 22:14:07 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-27 22:14:07 (8458) [INFO] error : Corrupt * 2024-11-27 22:14:07 (8475) [INFO] * 2024-11-27 22:14:07 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-27 22:14:07 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-27 22:14:07 (8445) [INFO] * 2024-11-27 22:14:11 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-27 22:14:11 (8445) [INFO] * 2024-11-27 22:14:11 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 22:14:11 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-27 22:14:12 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-27 22:14:12 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-27 22:14:12 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-27 22:14:12 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-27 22:14: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-27 22:14:12 (8458) [INFO] Trying other mirror. * 2024-11-27 22:14:12 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-27 22:14:12 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-27 22:14:12 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-27 22:14:12 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-27 22:14:12 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-27 22:14:12 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-27 22:14:12 (8458) [INFO] yum --disablerepo=base ... * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-27 22:14:12 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-27 22:14:12 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] yum-config-manager --disable base * 2024-11-27 22:14:12 (8458) [INFO] or * 2024-11-27 22:14:12 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-27 22:14:12 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-27 22:14:12 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-27 22:14:12 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-27 22:14:12 (8458) [INFO] compromise: * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-27 22:14:12 (8458) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-27 22:14: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-27 22:14:12 (8475) [INFO] * 2024-11-27 22:14:12 (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 22:14:12 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-27 22:14:12 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-27 22:14:12 (8445) [INFO] * 2024-11-27 22:14:12 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 22:14:13 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-27 22:14:13 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-27 22:14:13 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-27 22:14:13 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-27 22:14:13 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-27 22:14:13 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-27 22:14:13 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-27 22:14:13 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-27 22:14:13 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-27 22:14:13 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-27 22:14:13 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-27 22:14:13 (8475) [INFO] * 2024-11-27 22:14:13 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-27 22:14:13 (8445) [INFO] * 2024-11-27 22:14:13 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-27 22:14:13 (8458) [INFO] Determining fastest mirrors * 2024-11-27 22:14:14 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-27 22:14:14 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-27 22:14:14 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-27 22:14:14 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-27 22:14:15 (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 22:14:15 (8458) [INFO] Trying other mirror. * 2024-11-27 22:14:15 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-27 22:14:15 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-27 22:14:15 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-27 22:14:15 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-27 22:14:15 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-27 22:14:15 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-27 22:14:15 (8458) [INFO] yum --disablerepo=base ... * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-27 22:14:15 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-27 22:14:15 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] yum-config-manager --disable base * 2024-11-27 22:14:15 (8458) [INFO] or * 2024-11-27 22:14:15 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-27 22:14:15 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-27 22:14:15 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-27 22:14:15 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-27 22:14:15 (8458) [INFO] compromise: * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-27 22:14:15 (8458) [INFO] * 2024-11-27 22:14:15 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-27 22:14:15 (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 22:14:15 (8475) [INFO] * 2024-11-27 22:14:15 (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 22:14:15 (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 22:14:15 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-27 22:14:16 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FlJjyPSzdv/ea_profile.json * 2024-11-27 22:14:17 (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/FlJjyPSzdv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-27 22:14:17 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-28 22:13:45 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-28 22:13:45 (9517) [INFO] Script is up to date. * 2024-11-28 22:13:46 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-28 22:13:46 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-28 22:13:46 (8445) [INFO] * 2024-11-28 22:13:51 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-28 22:13:51 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-28 22:13:51 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-28 22:13:51 (8445) [INFO] * 2024-11-28 22:14:19 (8458) [INFO] promote_db.campaigns * 2024-11-28 22:14:19 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] promote_db.links * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] promote_db.subscribers * 2024-11-28 22:14:19 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_12_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_17_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_21_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_25_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_32_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_33_options * 2024-11-28 22:14:19 (8458) [INFO] warning : Table is marked as crashed * 2024-11-28 22:14:19 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-28 22:14:19 (8458) [INFO] error : Corrupt * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_35_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_35_postmeta * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_35_posts * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_35_term_relationships * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_35_term_taxonomy * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_37_options * 2024-11-28 22:14:19 (8458) [INFO] warning : Table is marked as crashed * 2024-11-28 22:14:19 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-28 22:14:19 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-28 22:14:19 (8458) [INFO] error : Corrupt * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_41_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_43_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_44_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_45_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_48_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_49_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_54_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_57_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_59_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_5_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_63_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_64_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_68_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_9_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_options * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-28 22:14:19 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-28 22:14:19 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-28 22:14:19 (8458) [INFO] warning : 5 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfissues * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-28 22:14:19 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfnotifications * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfreversecache * 2024-11-28 22:14:19 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-28 22:14:19 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-28 22:14:19 (8458) [INFO] websites_wp.rs_wfstatus * 2024-11-28 22:14:19 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-28 22:14:19 (8475) [INFO] * 2024-11-28 22:14:19 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): promote_db.campaigns warning : 5 clients are using or haven't closed the table properly promote_db.links warning : 4 clients are using or haven't closed the table properly promote_db.subscribers warning : 5 clients are using or haven't closed the table properly websites_wp.rs_12_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_17_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_21_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_25_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_32_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_35_postmeta warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_posts warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_relationships warning : 1 client is using or hasn't closed the table properly websites_wp.rs_35_term_taxonomy warning : 1 client is using or hasn't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_41_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_43_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_44_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_45_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_48_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_49_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_54_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_59_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_68_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 5 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 5 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 5 clients are using or haven't closed the table properly websites_wp.rs_wfissues warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wflivetraffichuman warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfnotifications warning : 1 client is using or hasn't closed the table properly websites_wp.rs_wfreversecache warning : 2 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfstatus warning : 1 client is using or hasn't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-28 22:14:19 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-28 22:14:19 (8445) [INFO] * 2024-11-28 22:14:24 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-28 22:14:24 (8445) [INFO] * 2024-11-28 22:14:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 22:14:24 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-28 22:14:25 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-28 22:14:25 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-28 22:14:25 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-28 22:14:25 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-28 22:14:25 (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 22:14:25 (8458) [INFO] Trying other mirror. * 2024-11-28 22:14:25 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-28 22:14:25 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-28 22:14:25 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-28 22:14:25 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-28 22:14:25 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-28 22:14:25 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-28 22:14:25 (8458) [INFO] yum --disablerepo=base ... * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-28 22:14:25 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-28 22:14:25 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] yum-config-manager --disable base * 2024-11-28 22:14:25 (8458) [INFO] or * 2024-11-28 22:14:25 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-28 22:14:25 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-28 22:14:25 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-28 22:14:25 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-28 22:14:25 (8458) [INFO] compromise: * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-28 22:14:25 (8458) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-28 22:14:25 (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 22:14:25 (8475) [INFO] * 2024-11-28 22:14:25 (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 22:14:25 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-28 22:14:25 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-28 22:14:25 (8445) [INFO] * 2024-11-28 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 22:14:25 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-28 22:14:25 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-28 22:14:25 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-28 22:14:25 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-28 22:14:25 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-28 22:14:25 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-28 22:14:25 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-28 22:14:25 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-28 22:14:25 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-28 22:14:25 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-28 22:14:25 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-28 22:14:25 (8475) [INFO] * 2024-11-28 22:14:25 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-28 22:14:25 (8445) [INFO] * 2024-11-28 22:14:26 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-28 22:14:26 (8458) [INFO] Determining fastest mirrors * 2024-11-28 22:14:27 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-28 22:14:27 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-28 22:14:27 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-28 22:14:27 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-28 22:14:27 (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 22:14:27 (8458) [INFO] Trying other mirror. * 2024-11-28 22:14:27 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-28 22:14:27 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-28 22:14:27 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-28 22:14:27 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-28 22:14:27 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-28 22:14:27 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-28 22:14:27 (8458) [INFO] yum --disablerepo=base ... * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-28 22:14:27 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-28 22:14:27 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] yum-config-manager --disable base * 2024-11-28 22:14:27 (8458) [INFO] or * 2024-11-28 22:14:27 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-28 22:14:27 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-28 22:14:27 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-28 22:14:27 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-28 22:14:27 (8458) [INFO] compromise: * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-28 22:14:27 (8458) [INFO] * 2024-11-28 22:14:27 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-28 22:14:27 (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 22:14:27 (8475) [INFO] * 2024-11-28 22:14:27 (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 22:14:27 (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 22:14:28 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-28 22:14:29 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/swq6zmxfRu/ea_profile.json * 2024-11-28 22:14:30 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/swq6zmxfRu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-28 22:14:30 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-29 22:13:35 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-29 22:13:35 (9517) [INFO] Script is up to date. * 2024-11-29 22:13:36 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-29 22:13:36 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-29 22:13:36 (8445) [INFO] * 2024-11-29 22:13:39 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-29 22:13:39 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-29 22:13:39 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-29 22:13:39 (8445) [INFO] * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_12_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_12_postmeta * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_12_posts * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_12_term_relationships * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_12_term_taxonomy * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_21_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_31_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_33_options * 2024-11-29 22:13:54 (8458) [INFO] warning : Table is marked as crashed * 2024-11-29 22:13:54 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-29 22:13:54 (8458) [INFO] error : Corrupt * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_35_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_37_options * 2024-11-29 22:13:54 (8458) [INFO] warning : Table is marked as crashed * 2024-11-29 22:13:54 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-29 22:13:54 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-29 22:13:54 (8458) [INFO] error : Corrupt * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_39_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_3_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_46_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_48_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_49_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 1 client is using or hasn't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_52_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_54_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_57_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_5_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_62_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_63_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 2 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_64_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_68_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_9_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_options * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_sitemeta * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfblockediplog * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfblocks7 * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfconfig * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfcrawlers * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfhits * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wflivetraffichuman * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wflogins * 2024-11-29 22:13:54 (8458) [INFO] warning : 3 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8458) [INFO] websites_wp.rs_wfsnipcache * 2024-11-29 22:13:54 (8458) [INFO] warning : 4 clients are using or haven't closed the table properly * 2024-11-29 22:13:54 (8475) [INFO] * 2024-11-29 22:13:54 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_12_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_12_postmeta warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_posts warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_relationships warning : 2 clients are using or haven't closed the table properly websites_wp.rs_12_term_taxonomy warning : 2 clients are using or haven't closed the table properly websites_wp.rs_21_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_31_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_35_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt websites_wp.rs_39_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_3_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_46_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_48_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_49_options warning : 1 client is using or hasn't closed the table properly websites_wp.rs_52_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_54_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_57_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_5_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_62_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_63_options warning : 2 clients are using or haven't closed the table properly websites_wp.rs_64_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_68_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_9_options warning : 3 clients are using or haven't closed the table properly websites_wp.rs_options warning : 4 clients are using or haven't closed the table properly websites_wp.rs_sitemeta warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfblockediplog warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfblocks7 warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfconfig warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wfcrawlers warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfhits warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wflivetraffichuman warning : 4 clients are using or haven't closed the table properly websites_wp.rs_wflogins warning : 3 clients are using or haven't closed the table properly websites_wp.rs_wfsnipcache warning : 4 clients are using or haven't closed the table properly You should repair any corrupted databases before elevating the system. * 2024-11-29 22:13:54 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-29 22:13:54 (8445) [INFO] * 2024-11-29 22:13:58 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-29 22:13:58 (8445) [INFO] * 2024-11-29 22:13:58 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 22:13:59 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-29 22:14:00 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-29 22:14:00 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-29 22:14:00 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-29 22:14:00 (8458) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-11-29 22:14:00 (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 22:14:00 (8458) [INFO] Trying other mirror. * 2024-11-29 22:14:00 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-29 22:14:00 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-29 22:14:00 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-29 22:14:00 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-29 22:14:00 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-29 22:14:00 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-29 22:14:00 (8458) [INFO] yum --disablerepo=base ... * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-29 22:14:00 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-29 22:14:00 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] yum-config-manager --disable base * 2024-11-29 22:14:00 (8458) [INFO] or * 2024-11-29 22:14:00 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-29 22:14:00 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-29 22:14:00 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-29 22:14:00 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-29 22:14:00 (8458) [INFO] compromise: * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-29 22:14:00 (8458) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-29 22:14:00 (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 22:14:00 (8475) [INFO] * 2024-11-29 22:14:00 (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 22:14:00 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-29 22:14:00 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-29 22:14:00 (8445) [INFO] * 2024-11-29 22:14:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 22:14:01 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-29 22:14:01 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-29 22:14:01 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-29 22:14:01 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-29 22:14:01 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-29 22:14:01 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-29 22:14:01 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-29 22:14:01 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-29 22:14:01 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-29 22:14:01 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-29 22:14:01 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-29 22:14:01 (8475) [INFO] * 2024-11-29 22:14:01 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-29 22:14:01 (8445) [INFO] * 2024-11-29 22:14:01 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-29 22:14:01 (8458) [INFO] Determining fastest mirrors * 2024-11-29 22:14:03 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-29 22:14:03 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-29 22:14:03 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-29 22:14:03 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-29 22:14:03 (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 22:14:03 (8458) [INFO] Trying other mirror. * 2024-11-29 22:14:03 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-29 22:14:03 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-29 22:14:03 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-29 22:14:03 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-29 22:14:03 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-29 22:14:03 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-29 22:14:03 (8458) [INFO] yum --disablerepo=base ... * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-29 22:14:03 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-29 22:14:03 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] yum-config-manager --disable base * 2024-11-29 22:14:03 (8458) [INFO] or * 2024-11-29 22:14:03 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-29 22:14:03 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-29 22:14:03 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-29 22:14:03 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-29 22:14:03 (8458) [INFO] compromise: * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-29 22:14:03 (8458) [INFO] * 2024-11-29 22:14:03 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-29 22:14:03 (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 22:14:03 (8475) [INFO] * 2024-11-29 22:14:03 (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 22:14:03 (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 22:14:03 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-29 22:14:04 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LgnFwRbJ7h/ea_profile.json * 2024-11-29 22:14:06 (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/LgnFwRbJ7h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-29 22:14:06 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-11-30 22:14:38 (9495) [INFO] Self-update of script version 58 requested. * 2024-11-30 22:14:38 (9517) [INFO] Script is up to date. * 2024-11-30 22:14:39 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-11-30 22:14:39 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-11-30 22:14:39 (8445) [INFO] * 2024-11-30 22:14:43 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-11-30 22:14:43 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-11-30 22:14:43 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-11-30 22:14:43 (8445) [INFO] * 2024-11-30 22:15:03 (8458) [INFO] websites_wp.rs_33_options * 2024-11-30 22:15:03 (8458) [INFO] warning : Table is marked as crashed * 2024-11-30 22:15:03 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-11-30 22:15:03 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-11-30 22:15:03 (8458) [INFO] error : Corrupt * 2024-11-30 22:15:03 (8458) [INFO] websites_wp.rs_37_options * 2024-11-30 22:15:03 (8458) [INFO] warning : Table is marked as crashed * 2024-11-30 22:15:03 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-11-30 22:15:03 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-11-30 22:15:03 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-11-30 22:15:03 (8458) [INFO] error : Corrupt * 2024-11-30 22:15:03 (8475) [INFO] * 2024-11-30 22:15:03 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-11-30 22:15:03 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-11-30 22:15:03 (8445) [INFO] * 2024-11-30 22:15:07 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-30 22:15:07 (8445) [INFO] * 2024-11-30 22:15:08 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 22:15:08 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-11-30 22:15:09 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-30 22:15:09 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-30 22:15:09 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-30 22:15:09 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-11-30 22:15:09 (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 22:15:09 (8458) [INFO] Trying other mirror. * 2024-11-30 22:15:09 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-30 22:15:09 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-30 22:15:09 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-30 22:15:09 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-30 22:15:09 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-30 22:15:09 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-30 22:15:09 (8458) [INFO] yum --disablerepo=base ... * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-30 22:15:09 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-30 22:15:09 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] yum-config-manager --disable base * 2024-11-30 22:15:09 (8458) [INFO] or * 2024-11-30 22:15:09 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-30 22:15:09 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-30 22:15:09 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-30 22:15:09 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-30 22:15:09 (8458) [INFO] compromise: * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-30 22:15:09 (8458) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-30 22:15:09 (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 22:15:09 (8475) [INFO] * 2024-11-30 22:15:09 (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 22:15:09 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-11-30 22:15:09 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-11-30 22:15:09 (8445) [INFO] * 2024-11-30 22:15:09 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 22:15:10 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-11-30 22:15:10 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-11-30 22:15:10 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-11-30 22:15:10 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-11-30 22:15:10 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-11-30 22:15:10 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-11-30 22:15:10 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-11-30 22:15:10 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-11-30 22:15:10 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-11-30 22:15:10 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-11-30 22:15:10 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-11-30 22:15:10 (8475) [INFO] * 2024-11-30 22:15:10 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-11-30 22:15:10 (8445) [INFO] * 2024-11-30 22:15:10 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-11-30 22:15:10 (8458) [INFO] Determining fastest mirrors * 2024-11-30 22:15:13 (8458) [INFO] * EA4: 185.15.22.168 * 2024-11-30 22:15:13 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-11-30 22:15:13 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-11-30 22:15:13 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-11-30 22:15:14 (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 22:15:14 (8458) [INFO] Trying other mirror. * 2024-11-30 22:15:14 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-11-30 22:15:14 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-11-30 22:15:14 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-11-30 22:15:14 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-11-30 22:15:14 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-11-30 22:15:14 (8458) [INFO] packages for the previous distribution release still work). * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-11-30 22:15:14 (8458) [INFO] yum --disablerepo=base ... * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-11-30 22:15:14 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-11-30 22:15:14 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] yum-config-manager --disable base * 2024-11-30 22:15:14 (8458) [INFO] or * 2024-11-30 22:15:14 (8458) [INFO] subscription-manager repos --disable=base * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-11-30 22:15:14 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-11-30 22:15:14 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-11-30 22:15:14 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-11-30 22:15:14 (8458) [INFO] compromise: * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-11-30 22:15:14 (8458) [INFO] * 2024-11-30 22:15:14 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-11-30 22:15:14 (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 22:15:14 (8475) [INFO] * 2024-11-30 22:15:14 (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 22:15:14 (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 22:15:14 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-11-30 22:15:15 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3O89hBl9yW/ea_profile.json * 2024-11-30 22:15:17 (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/3O89hBl9yW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-11-30 22:15:17 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-01 22:14:33 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-01 22:14:33 (9517) [INFO] Script is up to date. * 2024-12-01 22:14:34 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-01 22:14:34 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-01 22:14:34 (8445) [INFO] * 2024-12-01 22:14:37 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-01 22:14:37 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-01 22:14:37 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-01 22:14:37 (8445) [INFO] * 2024-12-01 22:14:58 (8458) [INFO] websites_wp.rs_33_options * 2024-12-01 22:14:58 (8458) [INFO] warning : Table is marked as crashed * 2024-12-01 22:14:58 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-12-01 22:14:58 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-12-01 22:14:58 (8458) [INFO] error : Corrupt * 2024-12-01 22:14:58 (8458) [INFO] websites_wp.rs_37_options * 2024-12-01 22:14:58 (8458) [INFO] warning : Table is marked as crashed * 2024-12-01 22:14:58 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-12-01 22:14:58 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-12-01 22:14:58 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-12-01 22:14:58 (8458) [INFO] error : Corrupt * 2024-12-01 22:14:58 (8475) [INFO] * 2024-12-01 22:14:58 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-12-01 22:14:58 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-01 22:14:58 (8445) [INFO] * 2024-12-01 22:15:01 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-01 22:15:01 (8445) [INFO] * 2024-12-01 22:15:02 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 22:15:03 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-01 22:15:03 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-01 22:15:03 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-01 22:15:03 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-01 22:15:03 (8458) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-01 22:15: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-12-01 22:15:04 (8458) [INFO] Trying other mirror. * 2024-12-01 22:15:04 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-01 22:15:04 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-01 22:15:04 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-01 22:15:04 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-01 22:15:04 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-01 22:15:04 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-01 22:15:04 (8458) [INFO] yum --disablerepo=base ... * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-01 22:15:04 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-01 22:15:04 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] yum-config-manager --disable base * 2024-12-01 22:15:04 (8458) [INFO] or * 2024-12-01 22:15:04 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-01 22:15:04 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-01 22:15:04 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-01 22:15:04 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-01 22:15:04 (8458) [INFO] compromise: * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-01 22:15:04 (8458) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-01 22:15: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-12-01 22:15:04 (8475) [INFO] * 2024-12-01 22:15:04 (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 22:15:04 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-01 22:15:04 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-01 22:15:04 (8445) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 22:15:04 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-01 22:15:04 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-01 22:15:04 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-01 22:15:04 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-01 22:15:04 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-01 22:15:04 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-01 22:15:04 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-01 22:15:04 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-01 22:15:04 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-01 22:15:04 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-01 22:15:04 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-01 22:15:04 (8475) [INFO] * 2024-12-01 22:15:04 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-01 22:15:04 (8445) [INFO] * 2024-12-01 22:15:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-01 22:15:05 (8458) [INFO] Determining fastest mirrors * 2024-12-01 22:15:09 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-01 22:15:09 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-01 22:15:09 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-01 22:15:09 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-12-01 22:15:09 (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 22:15:09 (8458) [INFO] Trying other mirror. * 2024-12-01 22:15:09 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-01 22:15:09 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-01 22:15:09 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-01 22:15:09 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-01 22:15:09 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-01 22:15:09 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-01 22:15:09 (8458) [INFO] yum --disablerepo=base ... * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-01 22:15:09 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-01 22:15:09 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] yum-config-manager --disable base * 2024-12-01 22:15:09 (8458) [INFO] or * 2024-12-01 22:15:09 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-01 22:15:09 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-01 22:15:09 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-01 22:15:09 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-01 22:15:09 (8458) [INFO] compromise: * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-01 22:15:09 (8458) [INFO] * 2024-12-01 22:15:09 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-01 22:15:09 (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 22:15:09 (8475) [INFO] * 2024-12-01 22:15:09 (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 22:15:09 (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 22:15:09 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-01 22:15:10 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O6hPBAYbkX/ea_profile.json * 2024-12-01 22:15:11 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/O6hPBAYbkX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-12-01 22:15:11 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-02 22:13:41 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-02 22:13:41 (9517) [INFO] Script is up to date. * 2024-12-02 22:13:43 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-02 22:13:43 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-02 22:13:43 (8445) [INFO] * 2024-12-02 22:13:46 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-02 22:13:46 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-02 22:13:46 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-02 22:13:46 (8445) [INFO] * 2024-12-02 22:14:05 (8458) [INFO] websites_wp.rs_33_options * 2024-12-02 22:14:05 (8458) [INFO] warning : Table is marked as crashed * 2024-12-02 22:14:05 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-12-02 22:14:05 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-12-02 22:14:05 (8458) [INFO] error : Corrupt * 2024-12-02 22:14:05 (8458) [INFO] websites_wp.rs_37_options * 2024-12-02 22:14:05 (8458) [INFO] warning : Table is marked as crashed * 2024-12-02 22:14:05 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-12-02 22:14:05 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-12-02 22:14:05 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-12-02 22:14:05 (8458) [INFO] error : Corrupt * 2024-12-02 22:14:05 (8475) [INFO] * 2024-12-02 22:14:05 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-12-02 22:14:05 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-02 22:14:05 (8445) [INFO] * 2024-12-02 22:14:09 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-02 22:14:09 (8445) [INFO] * 2024-12-02 22:14:10 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 22:14:10 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-02 22:14:12 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-02 22:14:12 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-02 22:14:12 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-02 22:14:12 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-12-02 22:14: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-12-02 22:14:12 (8458) [INFO] Trying other mirror. * 2024-12-02 22:14:12 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-02 22:14:12 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-02 22:14:12 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-02 22:14:12 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-02 22:14:12 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-02 22:14:12 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-02 22:14:12 (8458) [INFO] yum --disablerepo=base ... * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-02 22:14:12 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-02 22:14:12 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] yum-config-manager --disable base * 2024-12-02 22:14:12 (8458) [INFO] or * 2024-12-02 22:14:12 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-02 22:14:12 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-02 22:14:12 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-02 22:14:12 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-02 22:14:12 (8458) [INFO] compromise: * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-02 22:14:12 (8458) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-02 22:14: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-12-02 22:14:12 (8475) [INFO] * 2024-12-02 22:14:12 (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 22:14:12 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-02 22:14:12 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-02 22:14:12 (8445) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 22:14:12 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-02 22:14:12 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-02 22:14:12 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-02 22:14:12 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-02 22:14:12 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-02 22:14:12 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-02 22:14:12 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-02 22:14:12 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-02 22:14:12 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-02 22:14:12 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-02 22:14:12 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-02 22:14:12 (8475) [INFO] * 2024-12-02 22:14:12 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-02 22:14:12 (8445) [INFO] * 2024-12-02 22:14:12 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-02 22:14:12 (8458) [INFO] Determining fastest mirrors * 2024-12-02 22:14:15 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-02 22:14:15 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-02 22:14:15 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-02 22:14:15 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-12-02 22:14:15 (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 22:14:15 (8458) [INFO] Trying other mirror. * 2024-12-02 22:14:15 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-02 22:14:15 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-02 22:14:15 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-02 22:14:15 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-02 22:14:15 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-02 22:14:15 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-02 22:14:15 (8458) [INFO] yum --disablerepo=base ... * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-02 22:14:15 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-02 22:14:15 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] yum-config-manager --disable base * 2024-12-02 22:14:15 (8458) [INFO] or * 2024-12-02 22:14:15 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-02 22:14:15 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-02 22:14:15 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-02 22:14:15 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-02 22:14:15 (8458) [INFO] compromise: * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-02 22:14:15 (8458) [INFO] * 2024-12-02 22:14:15 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-02 22:14:15 (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 22:14:15 (8475) [INFO] * 2024-12-02 22:14:15 (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 22:14:15 (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 22:14:15 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-02 22:14:16 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0LvluTLWCa/ea_profile.json * 2024-12-02 22:14:19 (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/0LvluTLWCa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-12-02 22:14:19 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-03 22:13:44 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-03 22:13:44 (9517) [INFO] Script is up to date. * 2024-12-03 22:13:46 (249) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-03 22:13:46 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-03 22:13:46 (8445) [INFO] * 2024-12-03 22:13:52 (3710) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-03 22:13:52 (3717) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-03 22:13:52 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent * 2024-12-03 22:13:52 (8445) [INFO] * 2024-12-03 22:14:20 (8458) [INFO] websites_wp.rs_33_options * 2024-12-03 22:14:20 (8458) [INFO] warning : Table is marked as crashed * 2024-12-03 22:14:20 (8458) [INFO] warning : 67 clients are using or haven't closed the table properly * 2024-12-03 22:14:20 (8458) [INFO] error : Size of datafile is: 8421376 Should be: 8424260 * 2024-12-03 22:14:20 (8458) [INFO] error : Corrupt * 2024-12-03 22:14:20 (8458) [INFO] websites_wp.rs_37_options * 2024-12-03 22:14:20 (8458) [INFO] warning : Table is marked as crashed * 2024-12-03 22:14:20 (8458) [INFO] warning : 36 clients are using or haven't closed the table properly * 2024-12-03 22:14:20 (8458) [INFO] warning : Size of datafile is: 406824 Should be: 406740 * 2024-12-03 22:14:20 (8458) [INFO] error : Found 1057 keys of 1056 * 2024-12-03 22:14:20 (8458) [INFO] error : Corrupt * 2024-12-03 22:14:20 (8475) [INFO] * 2024-12-03 22:14:20 (249) [WARN] *** Elevation Blocker detected: *** We have found the following problems with your database(s): websites_wp.rs_33_options warning : Table is marked as crashed warning : 67 clients are using or haven't closed the table properly error : Size of datafile is: 8421376 Should be: 8424260 error : Corrupt websites_wp.rs_37_options warning : Table is marked as crashed warning : 36 clients are using or haven't closed the table properly warning : Size of datafile is: 406824 Should be: 406740 error : Found 1057 keys of 1056 error : Corrupt You should repair any corrupted databases before elevating the system. * 2024-12-03 22:14:20 (8444) [INFO] Running: /usr/bin/yum list extras * 2024-12-03 22:14:20 (8445) [INFO] * 2024-12-03 22:14:24 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-03 22:14:24 (8445) [INFO] * 2024-12-03 22:14:24 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 22:14:24 (8458) [INFO] Loading mirror speeds from cached hostfile * 2024-12-03 22:14:24 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-03 22:14:24 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-03 22:14:24 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-03 22:14:24 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-12-03 22:14:25 (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 22:14:25 (8458) [INFO] Trying other mirror. * 2024-12-03 22:14:25 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-03 22:14:25 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-03 22:14:25 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-03 22:14:25 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-03 22:14:25 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-03 22:14:25 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-03 22:14:25 (8458) [INFO] yum --disablerepo=base ... * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-03 22:14:25 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-03 22:14:25 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] yum-config-manager --disable base * 2024-12-03 22:14:25 (8458) [INFO] or * 2024-12-03 22:14:25 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-03 22:14:25 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-03 22:14:25 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-03 22:14:25 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-03 22:14:25 (8458) [INFO] compromise: * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-03 22:14:25 (8458) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-03 22:14:25 (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 22:14:25 (8475) [INFO] * 2024-12-03 22:14:25 (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 22:14:25 (5511) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-03 22:14:25 (8444) [INFO] Running: /usr/bin/yum clean all * 2024-12-03 22:14:25 (8445) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 22:14:25 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-03 22:14:25 (8458) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-03 22:14:25 (8458) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-03 22:14:25 (8458) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-03 22:14:25 (8458) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-03 22:14:25 (8458) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-03 22:14:25 (8458) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-03 22:14:25 (8458) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-03 22:14:25 (8458) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-03 22:14:25 (8458) [INFO] Cleaning up list of fastest mirrors * 2024-12-03 22:14:25 (8458) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-03 22:14:25 (8475) [INFO] * 2024-12-03 22:14:25 (8444) [INFO] Running: /usr/bin/yum makecache * 2024-12-03 22:14:25 (8445) [INFO] * 2024-12-03 22:14:25 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-03 22:14:25 (8458) [INFO] Determining fastest mirrors * 2024-12-03 22:14:27 (8458) [INFO] * EA4: 185.15.22.168 * 2024-12-03 22:14:27 (8458) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-03 22:14:27 (8458) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-03 22:14:27 (8458) [INFO] * epel: mirrors.hostiserver.com * 2024-12-03 22:14:27 (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 22:14:27 (8458) [INFO] Trying other mirror. * 2024-12-03 22:14:27 (8458) [INFO] To address this issue please refer to the below wiki article * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] https://wiki.centos.org/yum-errors * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-03 22:14:27 (8458) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-03 22:14:27 (8458) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-03 22:14:27 (8458) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-03 22:14:27 (8458) [INFO] distribution release than is supported by the repository (and the * 2024-12-03 22:14:27 (8458) [INFO] packages for the previous distribution release still work). * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-03 22:14:27 (8458) [INFO] yum --disablerepo=base ... * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-03 22:14:27 (8458) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-03 22:14:27 (8458) [INFO] again or use --enablerepo for temporary usage: * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] yum-config-manager --disable base * 2024-12-03 22:14:27 (8458) [INFO] or * 2024-12-03 22:14:27 (8458) [INFO] subscription-manager repos --disable=base * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-03 22:14:27 (8458) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-03 22:14:27 (8458) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-03 22:14:27 (8458) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-03 22:14:27 (8458) [INFO] compromise: * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-03 22:14:27 (8458) [INFO] * 2024-12-03 22:14:27 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-03 22:14:27 (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 22:14:27 (8475) [INFO] * 2024-12-03 22:14:27 (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 22:14:27 (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 22:14:27 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-03 22:14:28 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sd371lf2kh/ea_profile.json * 2024-12-03 22:14:29 (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/sd371lf2kh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587. * 2024-12-03 22:14:29 (439) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-04 22:13:44 (9495) [INFO] Self-update of script version 58 requested. * 2024-12-04 22:13:44 (9500) [INFO] Newer version of script found. Downloading. * 2024-12-04 22:13:45 (9509) [INFO] Script update to version 59 successful. * 2024-12-04 22:13:46 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-04 22:13:46 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-04 22:13:46 (9238) [INFO] * 2024-12-04 22:13:48 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-04 22:13:48 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-04 22:13:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-04 22:13:48 (9238) [INFO] * 2024-12-04 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-04 22:13:54 (9238) [INFO] * 2024-12-04 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 22:13:55 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-04 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-04 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-04 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-04 22:13:55 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-04 22:13: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-04 22:13:55 (9251) [INFO] Trying other mirror. * 2024-12-04 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-04 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-04 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-04 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-04 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-04 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-04 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-04 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-04 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2024-12-04 22:13:55 (9251) [INFO] or * 2024-12-04 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-04 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-04 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-04 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-04 22:13:55 (9251) [INFO] compromise: * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-04 22:13:55 (9251) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-04 22:13: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-04 22:13:55 (9268) [INFO] * 2024-12-04 22:13: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-04 22:13:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-04 22:13:55 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-04 22:13:55 (9238) [INFO] * 2024-12-04 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 22:13:56 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-04 22:13:56 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-04 22:13:56 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-04 22:13:56 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-04 22:13:56 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-04 22:13:56 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-04 22:13:56 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-04 22:13:56 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-04 22:13:56 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-04 22:13:56 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-04 22:13:56 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-04 22:13:56 (9268) [INFO] * 2024-12-04 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-04 22:13:56 (9238) [INFO] * 2024-12-04 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-04 22:13:56 (9251) [INFO] Determining fastest mirrors * 2024-12-04 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-04 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-04 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-04 22:13:57 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-04 22:13: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-04 22:13:57 (9251) [INFO] Trying other mirror. * 2024-12-04 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-04 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-04 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-04 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-04 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-04 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-04 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-04 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-04 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-04 22:13:57 (9251) [INFO] or * 2024-12-04 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-04 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-04 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-04 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-04 22:13:57 (9251) [INFO] compromise: * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-04 22:13:57 (9251) [INFO] * 2024-12-04 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-04 22:13: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-04 22:13:57 (9268) [INFO] * 2024-12-04 22:13: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-04 22:13: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-04 22:13:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-04 22:13:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1VDYuvLa6N/ea_profile.json * 2024-12-04 22:13: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/1VDYuvLa6N/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-04 22:13:59 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-05 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-05 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-05 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-05 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-05 22:13:45 (9238) [INFO] * 2024-12-05 22:13:50 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-05 22:13:50 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-05 22:13:50 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-05 22:13:50 (9238) [INFO] * 2024-12-05 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-05 22:13:53 (9238) [INFO] * 2024-12-05 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 22:13:53 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-05 22:13:54 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-05 22:13:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-05 22:13:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-05 22:13:54 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-05 22:13: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 22:13:54 (9251) [INFO] Trying other mirror. * 2024-12-05 22:13:54 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-05 22:13:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-05 22:13:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-05 22:13:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-05 22:13:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-05 22:13:54 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-05 22:13:54 (9251) [INFO] yum --disablerepo=base ... * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-05 22:13:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-05 22:13:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] yum-config-manager --disable base * 2024-12-05 22:13:54 (9251) [INFO] or * 2024-12-05 22:13:54 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-05 22:13:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-05 22:13:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-05 22:13:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-05 22:13:54 (9251) [INFO] compromise: * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-05 22:13:54 (9251) [INFO] * 2024-12-05 22:13:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-05 22:13: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 22:13:54 (9268) [INFO] * 2024-12-05 22:13: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 22:13:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-05 22:13:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-05 22:13:54 (9238) [INFO] * 2024-12-05 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 22:13:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-05 22:13:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-05 22:13:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-05 22:13:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-05 22:13:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-05 22:13:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-05 22:13:55 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-05 22:13:55 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-05 22:13:55 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-05 22:13:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-05 22:13:55 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-05 22:13:55 (9268) [INFO] * 2024-12-05 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-05 22:13:55 (9238) [INFO] * 2024-12-05 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-05 22:13:55 (9251) [INFO] Determining fastest mirrors * 2024-12-05 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-05 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-05 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-05 22:13:57 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-05 22:13: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-05 22:13:57 (9251) [INFO] Trying other mirror. * 2024-12-05 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-05 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-05 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-05 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-05 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-05 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-05 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-05 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-05 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-05 22:13:57 (9251) [INFO] or * 2024-12-05 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-05 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-05 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-05 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-05 22:13:57 (9251) [INFO] compromise: * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-05 22:13:57 (9251) [INFO] * 2024-12-05 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-05 22:13: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-05 22:13:57 (9268) [INFO] * 2024-12-05 22:13: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-05 22:13: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-05 22:13:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-05 22:13:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JSdB0cVPN4/ea_profile.json * 2024-12-05 22:13: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/JSdB0cVPN4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-05 22:13:59 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-06 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-06 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-06 22:13:46 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-06 22:13:46 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-06 22:13:46 (9238) [INFO] * 2024-12-06 22:13:49 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-06 22:13:49 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-06 22:13:49 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-06 22:13:49 (9238) [INFO] * 2024-12-06 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-06 22:13:54 (9238) [INFO] * 2024-12-06 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 22:13:55 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-06 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-06 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-06 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-06 22:13:56 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-06 22:13: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-06 22:13:56 (9251) [INFO] Trying other mirror. * 2024-12-06 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-06 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-06 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-06 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-06 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-06 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-06 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-06 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-06 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2024-12-06 22:13:56 (9251) [INFO] or * 2024-12-06 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-06 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-06 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-06 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-06 22:13:56 (9251) [INFO] compromise: * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-06 22:13:56 (9251) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-06 22:13: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-06 22:13:56 (9268) [INFO] * 2024-12-06 22:13: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-06 22:13:56 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-06 22:13:56 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-06 22:13:56 (9238) [INFO] * 2024-12-06 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 22:13:57 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-06 22:13:57 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-06 22:13:57 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-06 22:13:57 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-06 22:13:57 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-06 22:13:57 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-06 22:13:57 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-06 22:13:57 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-06 22:13:57 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-06 22:13:57 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-06 22:13:57 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-06 22:13:57 (9268) [INFO] * 2024-12-06 22:13:57 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-06 22:13:57 (9238) [INFO] * 2024-12-06 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-06 22:13:57 (9251) [INFO] Determining fastest mirrors * 2024-12-06 22:13:59 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-06 22:13:59 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-06 22:13:59 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-06 22:13:59 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-06 22:13: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-06 22:13:59 (9251) [INFO] Trying other mirror. * 2024-12-06 22:13:59 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-06 22:13:59 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-06 22:13:59 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-06 22:13:59 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-06 22:13:59 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-06 22:13:59 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-06 22:13:59 (9251) [INFO] yum --disablerepo=base ... * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-06 22:13:59 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-06 22:13:59 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] yum-config-manager --disable base * 2024-12-06 22:13:59 (9251) [INFO] or * 2024-12-06 22:13:59 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-06 22:13:59 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-06 22:13:59 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-06 22:13:59 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-06 22:13:59 (9251) [INFO] compromise: * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-06 22:13:59 (9251) [INFO] * 2024-12-06 22:13:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-06 22:13: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-06 22:13:59 (9268) [INFO] * 2024-12-06 22:13: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-06 22:13: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-06 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-06 22:14:00 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_j_YgkFEiN/ea_profile.json * 2024-12-06 22:14:02 (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/_j_YgkFEiN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-06 22:14:02 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-07 22:14:34 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-07 22:14:34 (10313) [INFO] Script is up to date. * 2024-12-07 22:14:35 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-07 22:14:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-07 22:14:35 (9238) [INFO] * 2024-12-07 22:14:38 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-07 22:14:38 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-07 22:14:38 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-07 22:14:38 (9238) [INFO] * 2024-12-07 22:14:42 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-07 22:14:42 (9238) [INFO] * 2024-12-07 22:14:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 22:14:42 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-07 22:14:43 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-07 22:14:43 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-07 22:14:43 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-07 22:14:43 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-07 22:14:43 (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 22:14:43 (9251) [INFO] Trying other mirror. * 2024-12-07 22:14:43 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-07 22:14:43 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-07 22:14:43 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-07 22:14:43 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-07 22:14:43 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-07 22:14:43 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-07 22:14:43 (9251) [INFO] yum --disablerepo=base ... * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-07 22:14:43 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-07 22:14:43 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] yum-config-manager --disable base * 2024-12-07 22:14:43 (9251) [INFO] or * 2024-12-07 22:14:43 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-07 22:14:43 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-07 22:14:43 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-07 22:14:43 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-07 22:14:43 (9251) [INFO] compromise: * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-07 22:14:43 (9251) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-07 22:14:43 (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 22:14:43 (9268) [INFO] * 2024-12-07 22:14:43 (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 22:14:43 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-07 22:14:43 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-07 22:14:43 (9238) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 22:14:43 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-07 22:14:43 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-07 22:14:43 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-07 22:14:43 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-07 22:14:43 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-07 22:14:43 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-07 22:14:43 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-07 22:14:43 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-07 22:14:43 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-07 22:14:43 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-07 22:14:43 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-07 22:14:43 (9268) [INFO] * 2024-12-07 22:14:43 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-07 22:14:43 (9238) [INFO] * 2024-12-07 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-07 22:14:43 (9251) [INFO] Determining fastest mirrors * 2024-12-07 22:14:45 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-07 22:14:45 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-07 22:14:45 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-07 22:14:45 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-07 22:14: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-07 22:14:45 (9251) [INFO] Trying other mirror. * 2024-12-07 22:14:45 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-07 22:14:45 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-07 22:14:45 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-07 22:14:45 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-07 22:14:45 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-07 22:14:45 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-07 22:14:45 (9251) [INFO] yum --disablerepo=base ... * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-07 22:14:45 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-07 22:14:45 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] yum-config-manager --disable base * 2024-12-07 22:14:45 (9251) [INFO] or * 2024-12-07 22:14:45 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-07 22:14:45 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-07 22:14:45 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-07 22:14:45 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-07 22:14:45 (9251) [INFO] compromise: * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-07 22:14:45 (9251) [INFO] * 2024-12-07 22:14:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-07 22:14: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-07 22:14:45 (9268) [INFO] * 2024-12-07 22:14: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-07 22:14: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-07 22:14:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-07 22:14:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/86EAkP591_/ea_profile.json * 2024-12-07 22:14: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/86EAkP591_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-07 22:14:47 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-08 22:14:34 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-08 22:14:34 (10313) [INFO] Script is up to date. * 2024-12-08 22:14:36 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-08 22:14:36 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-08 22:14:36 (9238) [INFO] * 2024-12-08 22:14:39 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-08 22:14:39 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-08 22:14:39 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-08 22:14:39 (9238) [INFO] * 2024-12-08 22:14:43 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-08 22:14:43 (9238) [INFO] * 2024-12-08 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 22:14:43 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-08 22:14:44 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-08 22:14:44 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-08 22:14:44 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-08 22:14:44 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-08 22:14: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-08 22:14:44 (9251) [INFO] Trying other mirror. * 2024-12-08 22:14:44 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-08 22:14:44 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-08 22:14:44 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-08 22:14:44 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-08 22:14:44 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-08 22:14:44 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-08 22:14:44 (9251) [INFO] yum --disablerepo=base ... * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-08 22:14:44 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-08 22:14:44 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] yum-config-manager --disable base * 2024-12-08 22:14:44 (9251) [INFO] or * 2024-12-08 22:14:44 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-08 22:14:44 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-08 22:14:44 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-08 22:14:44 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-08 22:14:44 (9251) [INFO] compromise: * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-08 22:14:44 (9251) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-08 22:14: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-08 22:14:44 (9268) [INFO] * 2024-12-08 22:14: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-08 22:14:44 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-08 22:14:44 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-08 22:14:44 (9238) [INFO] * 2024-12-08 22:14:44 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 22:14:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-08 22:14:45 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-08 22:14:45 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-08 22:14:45 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-08 22:14:45 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-08 22:14:45 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-08 22:14:45 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-08 22:14:45 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-08 22:14:45 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-08 22:14:45 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-08 22:14:45 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-08 22:14:45 (9268) [INFO] * 2024-12-08 22:14:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-08 22:14:45 (9238) [INFO] * 2024-12-08 22:14:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-08 22:14:45 (9251) [INFO] Determining fastest mirrors * 2024-12-08 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-08 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-08 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-08 22:14:47 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-08 22:14: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-08 22:14:47 (9251) [INFO] Trying other mirror. * 2024-12-08 22:14:47 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-08 22:14:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-08 22:14:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-08 22:14:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-08 22:14:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-08 22:14:47 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-08 22:14:47 (9251) [INFO] yum --disablerepo=base ... * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-08 22:14:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-08 22:14:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] yum-config-manager --disable base * 2024-12-08 22:14:47 (9251) [INFO] or * 2024-12-08 22:14:47 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-08 22:14:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-08 22:14:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-08 22:14:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-08 22:14:47 (9251) [INFO] compromise: * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-08 22:14:47 (9251) [INFO] * 2024-12-08 22:14:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-08 22:14: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-08 22:14:47 (9268) [INFO] * 2024-12-08 22:14:47 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-08 22:14:47 (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 22:14:48 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-08 22:14:48 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Td2tUJEoCv/ea_profile.json * 2024-12-08 22:14:50 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Td2tUJEoCv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-08 22:14:50 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-09 22:13:43 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-09 22:13:43 (10313) [INFO] Script is up to date. * 2024-12-09 22:13:44 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-09 22:13:44 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-09 22:13:44 (9238) [INFO] * 2024-12-09 22:13:47 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-09 22:13:47 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-09 22:13:47 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-09 22:13:47 (9238) [INFO] * 2024-12-09 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-09 22:13:52 (9238) [INFO] * 2024-12-09 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-09 22:13:54 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-09 22:13:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-09 22:13:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-09 22:13:54 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-09 22:13: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 22:13:54 (9251) [INFO] Trying other mirror. * 2024-12-09 22:13:54 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-09 22:13:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-09 22:13:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-09 22:13:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-09 22:13:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-09 22:13:54 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-09 22:13:54 (9251) [INFO] yum --disablerepo=base ... * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-09 22:13:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-09 22:13:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] yum-config-manager --disable base * 2024-12-09 22:13:54 (9251) [INFO] or * 2024-12-09 22:13:54 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-09 22:13:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-09 22:13:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-09 22:13:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-09 22:13:54 (9251) [INFO] compromise: * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-09 22:13:54 (9251) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-09 22:13: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 22:13:54 (9268) [INFO] * 2024-12-09 22:13: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-09 22:13:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-09 22:13:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-09 22:13:54 (9238) [INFO] * 2024-12-09 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 22:13:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-09 22:13:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-09 22:13:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-09 22:13:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-09 22:13:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-09 22:13:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-09 22:13:55 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-09 22:13:55 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-09 22:13:55 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-09 22:13:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-09 22:13:55 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-09 22:13:55 (9268) [INFO] * 2024-12-09 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-09 22:13:55 (9238) [INFO] * 2024-12-09 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-09 22:13:55 (9251) [INFO] Determining fastest mirrors * 2024-12-09 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-09 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-09 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-09 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-09 22:13: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-09 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-09 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-09 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-09 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-09 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-09 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-09 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-09 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-09 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-09 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-09 22:13:58 (9251) [INFO] or * 2024-12-09 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-09 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-09 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-09 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-09 22:13:58 (9251) [INFO] compromise: * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-09 22:13:58 (9251) [INFO] * 2024-12-09 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-09 22:13: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-09 22:13:58 (9268) [INFO] * 2024-12-09 22:13: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-09 22:13: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-09 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-09 22:14:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YSUBcWvQ1l/ea_profile.json * 2024-12-09 22:14: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/YSUBcWvQ1l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-09 22:14:03 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-10 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-10 22:13:46 (10313) [INFO] Script is up to date. * 2024-12-10 22:13:47 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-10 22:13:47 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-10 22:13:47 (9238) [INFO] * 2024-12-10 22:13:50 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-10 22:13:50 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-10 22:13:50 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-10 22:13:50 (9238) [INFO] * 2024-12-10 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-10 22:13:56 (9238) [INFO] * 2024-12-10 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-10 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-10 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-10 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-10 22:13:57 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-10 22:13: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-10 22:13:57 (9251) [INFO] Trying other mirror. * 2024-12-10 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-10 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-10 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-10 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-10 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-10 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-10 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-10 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-10 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-10 22:13:57 (9251) [INFO] or * 2024-12-10 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-10 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-10 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-10 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-10 22:13:57 (9251) [INFO] compromise: * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-10 22:13:57 (9251) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-10 22:13: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-10 22:13:57 (9268) [INFO] * 2024-12-10 22:13:57 (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 22:13:57 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-10 22:13:57 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-10 22:13:57 (9238) [INFO] * 2024-12-10 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 22:13:57 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-10 22:13:57 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-10 22:13:57 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-10 22:13:57 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-10 22:13:57 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-10 22:13:57 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-10 22:13:57 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-10 22:13:57 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-10 22:13:57 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-10 22:13:57 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-10 22:13:57 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-10 22:13:58 (9268) [INFO] * 2024-12-10 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-10 22:13:58 (9238) [INFO] * 2024-12-10 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-10 22:13:58 (9251) [INFO] Determining fastest mirrors * 2024-12-10 22:14:01 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-10 22:14:01 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-10 22:14:01 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-10 22:14:01 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-10 22:14: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-10 22:14:01 (9251) [INFO] Trying other mirror. * 2024-12-10 22:14:01 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-10 22:14:01 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-10 22:14:01 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-10 22:14:01 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-10 22:14:01 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-10 22:14:01 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-10 22:14:01 (9251) [INFO] yum --disablerepo=base ... * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-10 22:14:01 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-10 22:14:01 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] yum-config-manager --disable base * 2024-12-10 22:14:01 (9251) [INFO] or * 2024-12-10 22:14:01 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-10 22:14:01 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-10 22:14:01 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-10 22:14:01 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-10 22:14:01 (9251) [INFO] compromise: * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-10 22:14:01 (9251) [INFO] * 2024-12-10 22:14:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-10 22:14: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-10 22:14:01 (9268) [INFO] * 2024-12-10 22:14:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-10 22:14:01 (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 22:14:01 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-10 22:14:02 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cVU5F26xoZ/ea_profile.json * 2024-12-10 22:14: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/cVU5F26xoZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-10 22:14:04 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-11 22:14:13 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-11 22:14:13 (10313) [INFO] Script is up to date. * 2024-12-11 22:14:15 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-11 22:14:15 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-11 22:14:15 (9238) [INFO] * 2024-12-11 22:14:19 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-11 22:14:19 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-11 22:14:19 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-11 22:14:19 (9238) [INFO] * 2024-12-11 22:14:26 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-11 22:14:26 (9238) [INFO] * 2024-12-11 22:14:26 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 22:14:26 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-11 22:14:27 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-11 22:14:27 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-11 22:14:27 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-11 22:14:27 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-11 22:14: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 * 2024-12-11 22:14:28 (9251) [INFO] Trying other mirror. * 2024-12-11 22:14:28 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-11 22:14:28 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-11 22:14:28 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-11 22:14:28 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-11 22:14:28 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-11 22:14:28 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-11 22:14:28 (9251) [INFO] yum --disablerepo=base ... * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-11 22:14:28 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-11 22:14:28 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] yum-config-manager --disable base * 2024-12-11 22:14:28 (9251) [INFO] or * 2024-12-11 22:14:28 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-11 22:14:28 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-11 22:14:28 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-11 22:14:28 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-11 22:14:28 (9251) [INFO] compromise: * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-11 22:14:28 (9251) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-11 22:14: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 * 2024-12-11 22:14:28 (9268) [INFO] * 2024-12-11 22:14: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 * 2024-12-11 22:14:28 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-11 22:14:28 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-11 22:14:28 (9238) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 22:14:28 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-11 22:14:28 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-11 22:14:28 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-11 22:14:28 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-11 22:14:28 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-11 22:14:28 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-11 22:14:28 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-11 22:14:28 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-11 22:14:28 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-11 22:14:28 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-11 22:14:28 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-11 22:14:28 (9268) [INFO] * 2024-12-11 22:14:28 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-11 22:14:28 (9238) [INFO] * 2024-12-11 22:14:28 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-11 22:14:28 (9251) [INFO] Determining fastest mirrors * 2024-12-11 22:14:30 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-11 22:14:30 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-11 22:14:30 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-11 22:14:30 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-11 22:14:30 (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 22:14:30 (9251) [INFO] Trying other mirror. * 2024-12-11 22:14:30 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-11 22:14:30 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-11 22:14:30 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-11 22:14:30 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-11 22:14:30 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-11 22:14:30 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-11 22:14:30 (9251) [INFO] yum --disablerepo=base ... * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-11 22:14:30 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-11 22:14:30 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] yum-config-manager --disable base * 2024-12-11 22:14:30 (9251) [INFO] or * 2024-12-11 22:14:30 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-11 22:14:30 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-11 22:14:30 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-11 22:14:30 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-11 22:14:30 (9251) [INFO] compromise: * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-11 22:14:30 (9251) [INFO] * 2024-12-11 22:14:30 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-11 22:14:30 (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 22:14:30 (9268) [INFO] * 2024-12-11 22:14:30 (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 22:14:30 (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 22:14:31 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-11 22:14:31 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7M3bhnxPY_/ea_profile.json * 2024-12-11 22:14:33 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7M3bhnxPY_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-11 22:14:33 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-12 22:13:42 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-12 22:13:42 (10313) [INFO] Script is up to date. * 2024-12-12 22:13:43 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-12 22:13:43 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-12 22:13:43 (9238) [INFO] * 2024-12-12 22:13:46 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-12 22:13:46 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-12 22:13:46 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-12 22:13:46 (9238) [INFO] * 2024-12-12 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-12 22:13:51 (9238) [INFO] * 2024-12-12 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-12 22:13:53 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-12 22:13:53 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-12 22:13:53 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-12 22:13:53 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-12 22:13: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-12 22:13:53 (9251) [INFO] Trying other mirror. * 2024-12-12 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-12 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-12 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-12 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-12 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-12 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-12 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-12 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-12 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2024-12-12 22:13:53 (9251) [INFO] or * 2024-12-12 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-12 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-12 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-12 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-12 22:13:53 (9251) [INFO] compromise: * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-12 22:13:53 (9251) [INFO] * 2024-12-12 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-12 22:13: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-12 22:13:53 (9268) [INFO] * 2024-12-12 22:13: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 * 2024-12-12 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-12 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-12 22:13:53 (9238) [INFO] * 2024-12-12 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 22:13:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-12 22:13:54 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-12 22:13:54 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-12 22:13:54 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-12 22:13:54 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-12 22:13:54 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-12 22:13:54 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-12 22:13:54 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-12 22:13:54 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-12 22:13:54 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-12 22:13:54 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-12 22:13:54 (9268) [INFO] * 2024-12-12 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-12 22:13:54 (9238) [INFO] * 2024-12-12 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-12 22:13:54 (9251) [INFO] Determining fastest mirrors * 2024-12-12 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-12 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-12 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-12 22:13:56 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-12 22:13: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-12 22:13:56 (9251) [INFO] Trying other mirror. * 2024-12-12 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-12 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-12 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-12 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-12 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-12 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-12 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-12 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-12 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2024-12-12 22:13:56 (9251) [INFO] or * 2024-12-12 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-12 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-12 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-12 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-12 22:13:56 (9251) [INFO] compromise: * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-12 22:13:56 (9251) [INFO] * 2024-12-12 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-12 22:13: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-12 22:13:56 (9268) [INFO] * 2024-12-12 22:13: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-12 22:13: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-12 22:13:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-12 22:13:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xZVUulBrNj/ea_profile.json * 2024-12-12 22:13: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/xZVUulBrNj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-12 22:13:59 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-13 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-13 22:13:47 (10313) [INFO] Script is up to date. * 2024-12-13 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-13 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-13 22:13:48 (9238) [INFO] * 2024-12-13 22:13:52 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-13 22:13:52 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-13 22:13:52 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-13 22:13:52 (9238) [INFO] * 2024-12-13 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-13 22:13:56 (9238) [INFO] * 2024-12-13 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 22:13:57 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-13 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-13 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-13 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-13 22:13:57 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-13 22:13: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-13 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-13 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-13 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-13 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-13 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-13 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-13 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-13 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-13 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-13 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-13 22:13:58 (9251) [INFO] or * 2024-12-13 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-13 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-13 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-13 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-13 22:13:58 (9251) [INFO] compromise: * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-13 22:13:58 (9251) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-13 22:13: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-13 22:13:58 (9268) [INFO] * 2024-12-13 22:13: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-13 22:13:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-13 22:13:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-13 22:13:58 (9238) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 22:13:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-13 22:13:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-13 22:13:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-13 22:13:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-13 22:13:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-13 22:13:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-13 22:13:58 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-13 22:13:58 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-13 22:13:58 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-13 22:13:58 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-13 22:13:58 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-13 22:13:58 (9268) [INFO] * 2024-12-13 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-13 22:13:58 (9238) [INFO] * 2024-12-13 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-13 22:13:58 (9251) [INFO] Determining fastest mirrors * 2024-12-13 22:14:00 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-13 22:14:00 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-13 22:14:00 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-13 22:14:00 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-13 22:14: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-13 22:14:00 (9251) [INFO] Trying other mirror. * 2024-12-13 22:14:00 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-13 22:14:00 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-13 22:14:00 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-13 22:14:00 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-13 22:14:00 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-13 22:14:00 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-13 22:14:00 (9251) [INFO] yum --disablerepo=base ... * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-13 22:14:00 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-13 22:14:00 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] yum-config-manager --disable base * 2024-12-13 22:14:00 (9251) [INFO] or * 2024-12-13 22:14:00 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-13 22:14:00 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-13 22:14:00 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-13 22:14:00 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-13 22:14:00 (9251) [INFO] compromise: * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-13 22:14:00 (9251) [INFO] * 2024-12-13 22:14:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-13 22:14: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-13 22:14:00 (9268) [INFO] * 2024-12-13 22:14: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-13 22:14: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-13 22:14:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-13 22:14:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZIJcMCt5lD/ea_profile.json * 2024-12-13 22:14: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/ZIJcMCt5lD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-13 22:14:03 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-14 22:14:33 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-14 22:14:33 (10313) [INFO] Script is up to date. * 2024-12-14 22:14:34 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-14 22:14:34 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-14 22:14:34 (9238) [INFO] * 2024-12-14 22:14:37 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-14 22:14:37 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-14 22:14:37 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-14 22:14:37 (9238) [INFO] * 2024-12-14 22:14:43 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-14 22:14:43 (9238) [INFO] * 2024-12-14 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 22:14:43 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-14 22:14:44 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-14 22:14:44 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-14 22:14:44 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-14 22:14:44 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-14 22:14: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-14 22:14:44 (9251) [INFO] Trying other mirror. * 2024-12-14 22:14:44 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-14 22:14:44 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-14 22:14:44 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-14 22:14:44 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-14 22:14:44 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-14 22:14:44 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-14 22:14:44 (9251) [INFO] yum --disablerepo=base ... * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-14 22:14:44 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-14 22:14:44 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] yum-config-manager --disable base * 2024-12-14 22:14:44 (9251) [INFO] or * 2024-12-14 22:14:44 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-14 22:14:44 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-14 22:14:44 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-14 22:14:44 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-14 22:14:44 (9251) [INFO] compromise: * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-14 22:14:44 (9251) [INFO] * 2024-12-14 22:14:44 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-14 22:14: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-14 22:14:44 (9268) [INFO] * 2024-12-14 22:14: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-14 22:14:44 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-14 22:14:44 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-14 22:14:44 (9238) [INFO] * 2024-12-14 22:14:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 22:14:45 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-14 22:14:45 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-14 22:14:45 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-14 22:14:45 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-14 22:14:45 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-14 22:14:45 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-14 22:14:45 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-14 22:14:45 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-14 22:14:45 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-14 22:14:45 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-14 22:14:45 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-14 22:14:45 (9268) [INFO] * 2024-12-14 22:14:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-14 22:14:45 (9238) [INFO] * 2024-12-14 22:14:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-14 22:14:46 (9251) [INFO] Determining fastest mirrors * 2024-12-14 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-14 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-14 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-14 22:14:47 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-14 22:14: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-14 22:14:47 (9251) [INFO] Trying other mirror. * 2024-12-14 22:14:47 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-14 22:14:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-14 22:14:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-14 22:14:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-14 22:14:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-14 22:14:47 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-14 22:14:47 (9251) [INFO] yum --disablerepo=base ... * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-14 22:14:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-14 22:14:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] yum-config-manager --disable base * 2024-12-14 22:14:47 (9251) [INFO] or * 2024-12-14 22:14:47 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-14 22:14:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-14 22:14:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-14 22:14:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-14 22:14:47 (9251) [INFO] compromise: * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-14 22:14:47 (9251) [INFO] * 2024-12-14 22:14:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-14 22:14: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-14 22:14:47 (9268) [INFO] * 2024-12-14 22:14:47 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-14 22:14:47 (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 22:14:47 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-14 22:14:49 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/s4Fcd3zlvx/ea_profile.json * 2024-12-14 22:14:50 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/s4Fcd3zlvx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-14 22:14:50 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-15 22:14:42 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-15 22:14:42 (10313) [INFO] Script is up to date. * 2024-12-15 22:14:43 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-15 22:14:43 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-15 22:14:43 (9238) [INFO] * 2024-12-15 22:14:47 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-15 22:14:47 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-15 22:14:47 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-15 22:14:47 (9238) [INFO] * 2024-12-15 22:14:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-15 22:14:52 (9238) [INFO] * 2024-12-15 22:14:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 22:14:53 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-15 22:14:54 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-15 22:14:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-15 22:14:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-15 22:14:54 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-15 22:14: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-15 22:14:54 (9251) [INFO] Trying other mirror. * 2024-12-15 22:14:54 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-15 22:14:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-15 22:14:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-15 22:14:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-15 22:14:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-15 22:14:54 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-15 22:14:54 (9251) [INFO] yum --disablerepo=base ... * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-15 22:14:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-15 22:14:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] yum-config-manager --disable base * 2024-12-15 22:14:54 (9251) [INFO] or * 2024-12-15 22:14:54 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-15 22:14:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-15 22:14:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-15 22:14:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-15 22:14:54 (9251) [INFO] compromise: * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-15 22:14:54 (9251) [INFO] * 2024-12-15 22:14:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-15 22:14: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-15 22:14:54 (9268) [INFO] * 2024-12-15 22:14: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-15 22:14:54 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-15 22:14:54 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-15 22:14:54 (9238) [INFO] * 2024-12-15 22:14:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 22:14:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-15 22:14:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-15 22:14:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-15 22:14:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-15 22:14:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-15 22:14:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-15 22:14:55 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-15 22:14:55 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-15 22:14:55 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-15 22:14:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-15 22:14:55 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-15 22:14:55 (9268) [INFO] * 2024-12-15 22:14:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-15 22:14:55 (9238) [INFO] * 2024-12-15 22:14:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-15 22:14:55 (9251) [INFO] Determining fastest mirrors * 2024-12-15 22:14:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-15 22:14:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-15 22:14:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-15 22:14:57 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-15 22:14: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-15 22:14:57 (9251) [INFO] Trying other mirror. * 2024-12-15 22:14:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-15 22:14:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-15 22:14:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-15 22:14:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-15 22:14:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-15 22:14:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-15 22:14:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-15 22:14:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-15 22:14:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-15 22:14:57 (9251) [INFO] or * 2024-12-15 22:14:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-15 22:14:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-15 22:14:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-15 22:14:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-15 22:14:57 (9251) [INFO] compromise: * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-15 22:14:57 (9251) [INFO] * 2024-12-15 22:14:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-15 22:14: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-15 22:14:57 (9268) [INFO] * 2024-12-15 22:14: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-15 22:14: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-15 22:14:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-15 22:14:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lgMHTcu4uQ/ea_profile.json * 2024-12-15 22:15: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/lgMHTcu4uQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-15 22:15:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-16 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-16 22:13:46 (10313) [INFO] Script is up to date. * 2024-12-16 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-16 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-16 22:13:48 (9238) [INFO] * 2024-12-16 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-16 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-16 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-16 22:13:51 (9238) [INFO] * 2024-12-16 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-16 22:13:56 (9238) [INFO] * 2024-12-16 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-16 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-16 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-16 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-16 22:13:58 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-16 22:13: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-16 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-16 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-16 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-16 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-16 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-16 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-16 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-16 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-16 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-16 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-16 22:13:58 (9251) [INFO] or * 2024-12-16 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-16 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-16 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-16 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-16 22:13:58 (9251) [INFO] compromise: * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-16 22:13:58 (9251) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-16 22:13: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-16 22:13:58 (9268) [INFO] * 2024-12-16 22:13: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-16 22:13:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-16 22:13:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-16 22:13:58 (9238) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 22:13:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-16 22:13:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-16 22:13:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-16 22:13:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-16 22:13:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-16 22:13:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-16 22:13:58 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-16 22:13:58 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-16 22:13:58 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-16 22:13:58 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-16 22:13:58 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-16 22:13:58 (9268) [INFO] * 2024-12-16 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-16 22:13:58 (9238) [INFO] * 2024-12-16 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-16 22:13:59 (9251) [INFO] Determining fastest mirrors * 2024-12-16 22:14:02 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-16 22:14:02 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-16 22:14:02 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-16 22:14:02 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-16 22:14: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-16 22:14:02 (9251) [INFO] Trying other mirror. * 2024-12-16 22:14:02 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-16 22:14:02 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-16 22:14:02 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-16 22:14:02 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-16 22:14:02 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-16 22:14:02 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-16 22:14:02 (9251) [INFO] yum --disablerepo=base ... * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-16 22:14:02 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-16 22:14:02 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] yum-config-manager --disable base * 2024-12-16 22:14:02 (9251) [INFO] or * 2024-12-16 22:14:02 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-16 22:14:02 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-16 22:14:02 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-16 22:14:02 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-16 22:14:02 (9251) [INFO] compromise: * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-16 22:14:02 (9251) [INFO] * 2024-12-16 22:14:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-16 22:14: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-16 22:14:02 (9268) [INFO] * 2024-12-16 22:14: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-16 22:14: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-16 22:14:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-16 22:14:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UPTPFmdJCR/ea_profile.json * 2024-12-16 22:14: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/UPTPFmdJCR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-16 22:14:05 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-17 22:13:45 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-17 22:13:45 (10313) [INFO] Script is up to date. * 2024-12-17 22:13:46 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-17 22:13:46 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-17 22:13:46 (9238) [INFO] * 2024-12-17 22:13:49 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-17 22:13:49 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-17 22:13:49 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-17 22:13:49 (9238) [INFO] * 2024-12-17 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-17 22:13:54 (9238) [INFO] * 2024-12-17 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 22:13:55 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-17 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-17 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-17 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-17 22:13:56 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-17 22:13: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-17 22:13:56 (9251) [INFO] Trying other mirror. * 2024-12-17 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-17 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-17 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-17 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-17 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-17 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-17 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-17 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-17 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2024-12-17 22:13:56 (9251) [INFO] or * 2024-12-17 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-17 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-17 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-17 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-17 22:13:56 (9251) [INFO] compromise: * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-17 22:13:56 (9251) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-17 22:13: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-17 22:13:56 (9268) [INFO] * 2024-12-17 22:13: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-17 22:13:56 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-17 22:13:56 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-17 22:13:56 (9238) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 22:13:56 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-17 22:13:56 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-17 22:13:56 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-17 22:13:56 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-17 22:13:56 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-17 22:13:56 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-17 22:13:56 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-17 22:13:56 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-17 22:13:56 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-17 22:13:56 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-17 22:13:56 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-17 22:13:56 (9268) [INFO] * 2024-12-17 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-17 22:13:56 (9238) [INFO] * 2024-12-17 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-17 22:13:57 (9251) [INFO] Determining fastest mirrors * 2024-12-17 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-17 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-17 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-17 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-17 22:13: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 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-17 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-17 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-17 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-17 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-17 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-17 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-17 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-17 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-17 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-17 22:13:58 (9251) [INFO] or * 2024-12-17 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-17 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-17 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-17 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-17 22:13:58 (9251) [INFO] compromise: * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-17 22:13:58 (9251) [INFO] * 2024-12-17 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-17 22:13: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 22:13:58 (9268) [INFO] * 2024-12-17 22:13: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-17 22:13: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-17 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-17 22:14:00 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oLsA2mp9df/ea_profile.json * 2024-12-17 22:14: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/oLsA2mp9df/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-17 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-18 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-18 22:13:47 (10313) [INFO] Script is up to date. * 2024-12-18 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-18 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-18 22:13:48 (9238) [INFO] * 2024-12-18 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-18 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-18 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-18 22:13:51 (9238) [INFO] * 2024-12-18 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-18 22:13:55 (9238) [INFO] * 2024-12-18 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 22:13:55 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-18 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-18 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-18 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-18 22:13:56 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-18 22:13: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-18 22:13:56 (9251) [INFO] Trying other mirror. * 2024-12-18 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-18 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-18 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-18 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-18 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-18 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-18 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-18 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-18 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2024-12-18 22:13:56 (9251) [INFO] or * 2024-12-18 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-18 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-18 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-18 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-18 22:13:56 (9251) [INFO] compromise: * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-18 22:13:56 (9251) [INFO] * 2024-12-18 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-18 22:13: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-18 22:13:56 (9268) [INFO] * 2024-12-18 22:13: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-18 22:13:56 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-18 22:13:56 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-18 22:13:56 (9238) [INFO] * 2024-12-18 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 22:13:57 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-18 22:13:57 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-18 22:13:57 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-18 22:13:57 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-18 22:13:57 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-18 22:13:57 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-18 22:13:57 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-18 22:13:57 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-18 22:13:57 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-18 22:13:57 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-18 22:13:57 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-18 22:13:57 (9268) [INFO] * 2024-12-18 22:13:57 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-18 22:13:57 (9238) [INFO] * 2024-12-18 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-18 22:13:57 (9251) [INFO] Determining fastest mirrors * 2024-12-18 22:14:00 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-18 22:14:00 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-18 22:14:00 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-18 22:14:00 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-18 22:14: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-18 22:14:00 (9251) [INFO] Trying other mirror. * 2024-12-18 22:14:00 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-18 22:14:00 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-18 22:14:00 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-18 22:14:00 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-18 22:14:00 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-18 22:14:00 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-18 22:14:00 (9251) [INFO] yum --disablerepo=base ... * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-18 22:14:00 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-18 22:14:00 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] yum-config-manager --disable base * 2024-12-18 22:14:00 (9251) [INFO] or * 2024-12-18 22:14:00 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-18 22:14:00 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-18 22:14:00 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-18 22:14:00 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-18 22:14:00 (9251) [INFO] compromise: * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-18 22:14:00 (9251) [INFO] * 2024-12-18 22:14:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-18 22:14: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-18 22:14:01 (9268) [INFO] * 2024-12-18 22:14:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-18 22:14:01 (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 22:14:01 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-18 22:14:02 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L946CXZwgl/ea_profile.json * 2024-12-18 22:14: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/L946CXZwgl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-18 22:14:03 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-19 22:13:47 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-19 22:13:48 (10313) [INFO] Script is up to date. * 2024-12-19 22:13:49 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-19 22:13:49 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-19 22:13:49 (9238) [INFO] * 2024-12-19 22:13:52 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-19 22:13:52 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-19 22:13:52 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-19 22:13:52 (9238) [INFO] * 2024-12-19 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-19 22:13:56 (9238) [INFO] * 2024-12-19 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-19 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-19 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-19 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-19 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-19 22:13: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-19 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-19 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-19 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-19 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-19 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-19 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-19 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-19 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-19 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-19 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-19 22:13:58 (9251) [INFO] or * 2024-12-19 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-19 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-19 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-19 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-19 22:13:58 (9251) [INFO] compromise: * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-19 22:13:58 (9251) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-19 22:13: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-19 22:13:58 (9268) [INFO] * 2024-12-19 22:13: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-19 22:13:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-19 22:13:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-19 22:13:58 (9238) [INFO] * 2024-12-19 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 22:13:59 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-19 22:13:59 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-19 22:13:59 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-19 22:13:59 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-19 22:13:59 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-19 22:13:59 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-19 22:13:59 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-19 22:13:59 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-19 22:13:59 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-19 22:13:59 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-19 22:13:59 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-19 22:13:59 (9268) [INFO] * 2024-12-19 22:13:59 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-19 22:13:59 (9238) [INFO] * 2024-12-19 22:13:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-19 22:13:59 (9251) [INFO] Determining fastest mirrors * 2024-12-19 22:14:01 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-19 22:14:01 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-19 22:14:01 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-19 22:14:01 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-19 22:14: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-19 22:14:01 (9251) [INFO] Trying other mirror. * 2024-12-19 22:14:01 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-19 22:14:01 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-19 22:14:01 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-19 22:14:01 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-19 22:14:01 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-19 22:14:01 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-19 22:14:01 (9251) [INFO] yum --disablerepo=base ... * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-19 22:14:01 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-19 22:14:01 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] yum-config-manager --disable base * 2024-12-19 22:14:01 (9251) [INFO] or * 2024-12-19 22:14:01 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-19 22:14:01 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-19 22:14:01 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-19 22:14:01 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-19 22:14:01 (9251) [INFO] compromise: * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-19 22:14:01 (9251) [INFO] * 2024-12-19 22:14:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-19 22:14: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-19 22:14:01 (9268) [INFO] * 2024-12-19 22:14:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-19 22:14:01 (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 22:14:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-19 22:14:02 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NVfF3qpGBs/ea_profile.json * 2024-12-19 22:14: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/NVfF3qpGBs/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-19 22:14:04 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-20 22:13:42 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-20 22:13:42 (10313) [INFO] Script is up to date. * 2024-12-20 22:13:43 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-20 22:13:43 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-20 22:13:43 (9238) [INFO] * 2024-12-20 22:13:47 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-20 22:13:47 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-20 22:13:47 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-20 22:13:47 (9238) [INFO] * 2024-12-20 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-20 22:13:52 (9238) [INFO] * 2024-12-20 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 22:13:53 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-20 22:13:53 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-20 22:13:53 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-20 22:13:53 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-20 22:13:53 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-20 22:13: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-20 22:13:53 (9251) [INFO] Trying other mirror. * 2024-12-20 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-20 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-20 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-20 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-20 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-20 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-20 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-20 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-20 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2024-12-20 22:13:53 (9251) [INFO] or * 2024-12-20 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-20 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-20 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-20 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-20 22:13:53 (9251) [INFO] compromise: * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-20 22:13:53 (9251) [INFO] * 2024-12-20 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-20 22:13: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-20 22:13:53 (9268) [INFO] * 2024-12-20 22:13: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 * 2024-12-20 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-20 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-20 22:13:53 (9238) [INFO] * 2024-12-20 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 22:13:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-20 22:13:54 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-20 22:13:54 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-20 22:13:54 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-20 22:13:54 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-20 22:13:54 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-20 22:13:54 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-20 22:13:54 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-20 22:13:54 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-20 22:13:54 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-20 22:13:54 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-20 22:13:54 (9268) [INFO] * 2024-12-20 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-20 22:13:54 (9238) [INFO] * 2024-12-20 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-20 22:13:54 (9251) [INFO] Determining fastest mirrors * 2024-12-20 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-20 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-20 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-20 22:13:55 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-20 22:13: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-20 22:13:56 (9251) [INFO] Trying other mirror. * 2024-12-20 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-20 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-20 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-20 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-20 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-20 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-20 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-20 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-20 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2024-12-20 22:13:56 (9251) [INFO] or * 2024-12-20 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-20 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-20 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-20 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-20 22:13:56 (9251) [INFO] compromise: * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-20 22:13:56 (9251) [INFO] * 2024-12-20 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-20 22:13: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-20 22:13:56 (9268) [INFO] * 2024-12-20 22:13: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-20 22:13: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-20 22:13:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-20 22:13:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pK2hMxhiWf/ea_profile.json * 2024-12-20 22:13: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/pK2hMxhiWf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-20 22:13:58 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-21 22:14:37 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-21 22:14:38 (10313) [INFO] Script is up to date. * 2024-12-21 22:14:39 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-21 22:14:39 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-21 22:14:39 (9238) [INFO] * 2024-12-21 22:14:43 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-21 22:14:43 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-21 22:14:43 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-21 22:14:43 (9238) [INFO] * 2024-12-21 22:14:46 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-21 22:14:46 (9238) [INFO] * 2024-12-21 22:14:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 22:14:47 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-21 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-21 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-21 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-21 22:14:47 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-21 22:14: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-21 22:14:47 (9251) [INFO] Trying other mirror. * 2024-12-21 22:14:47 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-21 22:14:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-21 22:14:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-21 22:14:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-21 22:14:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-21 22:14:47 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-21 22:14:47 (9251) [INFO] yum --disablerepo=base ... * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-21 22:14:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-21 22:14:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] yum-config-manager --disable base * 2024-12-21 22:14:47 (9251) [INFO] or * 2024-12-21 22:14:47 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-21 22:14:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-21 22:14:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-21 22:14:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-21 22:14:47 (9251) [INFO] compromise: * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-21 22:14:47 (9251) [INFO] * 2024-12-21 22:14:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-21 22:14: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-21 22:14:47 (9268) [INFO] * 2024-12-21 22:14: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-21 22:14:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-21 22:14:47 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-21 22:14:47 (9238) [INFO] * 2024-12-21 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 22:14:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-21 22:14:48 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-21 22:14:48 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-21 22:14:48 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-21 22:14:48 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-21 22:14:48 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-21 22:14:48 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-21 22:14:48 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-21 22:14:48 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-21 22:14:48 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-21 22:14:48 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-21 22:14:48 (9268) [INFO] * 2024-12-21 22:14:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-21 22:14:48 (9238) [INFO] * 2024-12-21 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-21 22:14:48 (9251) [INFO] Determining fastest mirrors * 2024-12-21 22:14:49 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-21 22:14:49 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-21 22:14:49 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-21 22:14:49 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-21 22:14: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-21 22:14:49 (9251) [INFO] Trying other mirror. * 2024-12-21 22:14:49 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-21 22:14:49 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-21 22:14:49 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-21 22:14:49 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-21 22:14:49 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-21 22:14:49 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-21 22:14:49 (9251) [INFO] yum --disablerepo=base ... * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-21 22:14:49 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-21 22:14:49 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] yum-config-manager --disable base * 2024-12-21 22:14:49 (9251) [INFO] or * 2024-12-21 22:14:49 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-21 22:14:49 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-21 22:14:49 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-21 22:14:49 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-21 22:14:49 (9251) [INFO] compromise: * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-21 22:14:49 (9251) [INFO] * 2024-12-21 22:14:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-21 22:14: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-21 22:14:49 (9268) [INFO] * 2024-12-21 22:14:49 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2024-12-21 22:14:49 (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 22:14:50 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-21 22:14:51 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lYuGpmuPvY/ea_profile.json * 2024-12-21 22:14:52 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lYuGpmuPvY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-21 22:14:52 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-22 22:14:33 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-22 22:14:34 (10313) [INFO] Script is up to date. * 2024-12-22 22:14:35 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-22 22:14:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-22 22:14:35 (9238) [INFO] * 2024-12-22 22:14:38 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-22 22:14:38 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-22 22:14:38 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-22 22:14:38 (9238) [INFO] * 2024-12-22 22:14:42 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-22 22:14:42 (9238) [INFO] * 2024-12-22 22:14:42 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 22:14:42 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-22 22:14:42 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-22 22:14:42 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-22 22:14:42 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-22 22:14:42 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-22 22:14:43 (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 22:14:43 (9251) [INFO] Trying other mirror. * 2024-12-22 22:14:43 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-22 22:14:43 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-22 22:14:43 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-22 22:14:43 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-22 22:14:43 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-22 22:14:43 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-22 22:14:43 (9251) [INFO] yum --disablerepo=base ... * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-22 22:14:43 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-22 22:14:43 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] yum-config-manager --disable base * 2024-12-22 22:14:43 (9251) [INFO] or * 2024-12-22 22:14:43 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-22 22:14:43 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-22 22:14:43 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-22 22:14:43 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-22 22:14:43 (9251) [INFO] compromise: * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-22 22:14:43 (9251) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-22 22:14:43 (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 22:14:43 (9268) [INFO] * 2024-12-22 22:14:43 (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 22:14:43 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-22 22:14:43 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-22 22:14:43 (9238) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 22:14:43 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-22 22:14:43 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-22 22:14:43 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-22 22:14:43 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-22 22:14:43 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-22 22:14:43 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-22 22:14:43 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-22 22:14:43 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-22 22:14:43 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-22 22:14:43 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-22 22:14:43 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-22 22:14:43 (9268) [INFO] * 2024-12-22 22:14:43 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-22 22:14:43 (9238) [INFO] * 2024-12-22 22:14:43 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-22 22:14:43 (9251) [INFO] Determining fastest mirrors * 2024-12-22 22:14:45 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-22 22:14:45 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-22 22:14:45 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-22 22:14:45 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-22 22:14: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-22 22:14:45 (9251) [INFO] Trying other mirror. * 2024-12-22 22:14:45 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-22 22:14:45 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-22 22:14:45 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-22 22:14:45 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-22 22:14:45 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-22 22:14:45 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-22 22:14:45 (9251) [INFO] yum --disablerepo=base ... * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-22 22:14:45 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-22 22:14:45 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] yum-config-manager --disable base * 2024-12-22 22:14:45 (9251) [INFO] or * 2024-12-22 22:14:45 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-22 22:14:45 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-22 22:14:45 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-22 22:14:45 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-22 22:14:45 (9251) [INFO] compromise: * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-22 22:14:45 (9251) [INFO] * 2024-12-22 22:14:45 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-22 22:14: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-22 22:14:45 (9268) [INFO] * 2024-12-22 22:14: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-22 22:14: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-22 22:14:45 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-22 22:14:46 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wkxZR25I5G/ea_profile.json * 2024-12-22 22:14: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/wkxZR25I5G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-22 22:14:47 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-23 22:13:48 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-23 22:13:48 (10313) [INFO] Script is up to date. * 2024-12-23 22:13:49 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-23 22:13:49 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-23 22:13:49 (9238) [INFO] * 2024-12-23 22:13:52 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-23 22:13:52 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-23 22:13:52 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-23 22:13:52 (9238) [INFO] * 2024-12-23 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-23 22:13:56 (9238) [INFO] * 2024-12-23 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-23 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-23 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-23 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-23 22:13:57 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-23 22:13: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-23 22:13:57 (9251) [INFO] Trying other mirror. * 2024-12-23 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-23 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-23 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-23 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-23 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-23 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-23 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-23 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-23 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-23 22:13:57 (9251) [INFO] or * 2024-12-23 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-23 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-23 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-23 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-23 22:13:57 (9251) [INFO] compromise: * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-23 22:13:57 (9251) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-23 22:13: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-23 22:13:57 (9268) [INFO] * 2024-12-23 22:13:57 (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 22:13:57 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-23 22:13:57 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-23 22:13:57 (9238) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 22:13:57 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-23 22:13:57 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-23 22:13:57 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-23 22:13:57 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-23 22:13:57 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-23 22:13:57 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-23 22:13:57 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-23 22:13:57 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-23 22:13:57 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-23 22:13:57 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-23 22:13:57 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-23 22:13:57 (9268) [INFO] * 2024-12-23 22:13:57 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-23 22:13:57 (9238) [INFO] * 2024-12-23 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-23 22:13:58 (9251) [INFO] Determining fastest mirrors * 2024-12-23 22:13:59 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-23 22:13:59 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-23 22:13:59 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-23 22:13:59 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-23 22:13: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-23 22:13:59 (9251) [INFO] Trying other mirror. * 2024-12-23 22:13:59 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-23 22:13:59 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-23 22:13:59 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-23 22:13:59 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-23 22:13:59 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-23 22:13:59 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-23 22:13:59 (9251) [INFO] yum --disablerepo=base ... * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-23 22:13:59 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-23 22:13:59 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] yum-config-manager --disable base * 2024-12-23 22:13:59 (9251) [INFO] or * 2024-12-23 22:13:59 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-23 22:13:59 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-23 22:13:59 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-23 22:13:59 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-23 22:13:59 (9251) [INFO] compromise: * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-23 22:13:59 (9251) [INFO] * 2024-12-23 22:13:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-23 22:13: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-23 22:13:59 (9268) [INFO] * 2024-12-23 22:13: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-23 22:13: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-23 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-23 22:14:00 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cP7Qs5lMRw/ea_profile.json * 2024-12-23 22:14: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/cP7Qs5lMRw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-23 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-24 22:13:43 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-24 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-24 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-24 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-24 22:13:45 (9238) [INFO] * 2024-12-24 22:13:48 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-24 22:13:48 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-24 22:13:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-24 22:13:48 (9238) [INFO] * 2024-12-24 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-24 22:13:51 (9238) [INFO] * 2024-12-24 22:13:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 22:13:51 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-24 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-24 22:13:52 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-24 22:13:52 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-24 22:13:52 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-24 22:13: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 22:13:52 (9251) [INFO] Trying other mirror. * 2024-12-24 22:13:52 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-24 22:13:52 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-24 22:13:52 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-24 22:13:52 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-24 22:13:52 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-24 22:13:52 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-24 22:13:52 (9251) [INFO] yum --disablerepo=base ... * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-24 22:13:52 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-24 22:13:52 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] yum-config-manager --disable base * 2024-12-24 22:13:52 (9251) [INFO] or * 2024-12-24 22:13:52 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-24 22:13:52 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-24 22:13:52 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-24 22:13:52 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-24 22:13:52 (9251) [INFO] compromise: * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-24 22:13:52 (9251) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-24 22:13: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 22:13:52 (9268) [INFO] * 2024-12-24 22:13: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 22:13:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-24 22:13:52 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-24 22:13:52 (9238) [INFO] * 2024-12-24 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 22:13:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-24 22:13:52 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-24 22:13:52 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-24 22:13:52 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-24 22:13:52 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-24 22:13:52 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-24 22:13:52 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-24 22:13:52 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-24 22:13:52 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-24 22:13:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-24 22:13:52 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-24 22:13:52 (9268) [INFO] * 2024-12-24 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-24 22:13:52 (9238) [INFO] * 2024-12-24 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-24 22:13:53 (9251) [INFO] Determining fastest mirrors * 2024-12-24 22:13:54 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-24 22:13:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-24 22:13:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-24 22:13:54 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-24 22:13: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-24 22:13:54 (9251) [INFO] Trying other mirror. * 2024-12-24 22:13:54 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-24 22:13:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-24 22:13:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-24 22:13:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-24 22:13:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-24 22:13:54 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-24 22:13:54 (9251) [INFO] yum --disablerepo=base ... * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-24 22:13:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-24 22:13:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] yum-config-manager --disable base * 2024-12-24 22:13:54 (9251) [INFO] or * 2024-12-24 22:13:54 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-24 22:13:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-24 22:13:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-24 22:13:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-24 22:13:54 (9251) [INFO] compromise: * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-24 22:13:54 (9251) [INFO] * 2024-12-24 22:13:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-24 22:13: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-24 22:13:54 (9268) [INFO] * 2024-12-24 22:13: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-24 22:13: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-24 22:13:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-24 22:13:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dnLuhAwnVh/ea_profile.json * 2024-12-24 22:13: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/dnLuhAwnVh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-24 22:13:57 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-25 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-25 22:13:45 (10313) [INFO] Script is up to date. * 2024-12-25 22:13:46 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-25 22:13:46 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-25 22:13:46 (9238) [INFO] * 2024-12-25 22:13:49 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-25 22:13:49 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-25 22:13:49 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-25 22:13:49 (9238) [INFO] * 2024-12-25 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-25 22:13:53 (9238) [INFO] * 2024-12-25 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 22:13:53 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-25 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-25 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-25 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-25 22:13:55 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-25 22:13: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-25 22:13:55 (9251) [INFO] Trying other mirror. * 2024-12-25 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-25 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-25 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-25 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-25 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-25 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-25 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-25 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-25 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2024-12-25 22:13:55 (9251) [INFO] or * 2024-12-25 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-25 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-25 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-25 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-25 22:13:55 (9251) [INFO] compromise: * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-25 22:13:55 (9251) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-25 22:13: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-25 22:13:55 (9268) [INFO] * 2024-12-25 22:13: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-25 22:13:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-25 22:13:55 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-25 22:13:55 (9238) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 22:13:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-25 22:13:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-25 22:13:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-25 22:13:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-25 22:13:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-25 22:13:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-25 22:13:55 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-25 22:13:55 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-25 22:13:55 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-25 22:13:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-25 22:13:55 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-25 22:13:55 (9268) [INFO] * 2024-12-25 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-25 22:13:55 (9238) [INFO] * 2024-12-25 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-25 22:13:56 (9251) [INFO] Determining fastest mirrors * 2024-12-25 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-25 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-25 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-25 22:13:57 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-25 22:13: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-25 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-25 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-25 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-25 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-25 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-25 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-25 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-25 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-25 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-25 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-25 22:13:58 (9251) [INFO] or * 2024-12-25 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-25 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-25 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-25 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-25 22:13:58 (9251) [INFO] compromise: * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-25 22:13:58 (9251) [INFO] * 2024-12-25 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-25 22:13: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-25 22:13:58 (9268) [INFO] * 2024-12-25 22:13: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-25 22:13: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-25 22:13:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-25 22:13:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9cTuY9QuHd/ea_profile.json * 2024-12-25 22:14: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/9cTuY9QuHd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-25 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-26 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-26 22:13:46 (10313) [INFO] Script is up to date. * 2024-12-26 22:13:47 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-26 22:13:47 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-26 22:13:47 (9238) [INFO] * 2024-12-26 22:13:50 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-26 22:13:50 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-26 22:13:50 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-26 22:13:50 (9238) [INFO] * 2024-12-26 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-26 22:13:56 (9238) [INFO] * 2024-12-26 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 22:13:57 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-26 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-26 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-26 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-26 22:13:58 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-26 22:13: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-26 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-26 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-26 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-26 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-26 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-26 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-26 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-26 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-26 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-26 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-26 22:13:58 (9251) [INFO] or * 2024-12-26 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-26 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-26 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-26 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-26 22:13:58 (9251) [INFO] compromise: * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-26 22:13:58 (9251) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-26 22:13: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-26 22:13:58 (9268) [INFO] * 2024-12-26 22:13: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-26 22:13:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-26 22:13:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-26 22:13:58 (9238) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 22:13:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-26 22:13:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-26 22:13:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-26 22:13:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-26 22:13:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-26 22:13:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-26 22:13:58 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-26 22:13:58 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-26 22:13:58 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-26 22:13:58 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-26 22:13:58 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-26 22:13:58 (9268) [INFO] * 2024-12-26 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-26 22:13:58 (9238) [INFO] * 2024-12-26 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-26 22:13:59 (9251) [INFO] Determining fastest mirrors * 2024-12-26 22:14:00 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-26 22:14:00 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-26 22:14:00 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-26 22:14:00 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-26 22:14: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-26 22:14:00 (9251) [INFO] Trying other mirror. * 2024-12-26 22:14:00 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-26 22:14:00 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-26 22:14:00 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-26 22:14:00 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-26 22:14:00 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-26 22:14:00 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-26 22:14:00 (9251) [INFO] yum --disablerepo=base ... * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-26 22:14:00 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-26 22:14:00 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] yum-config-manager --disable base * 2024-12-26 22:14:00 (9251) [INFO] or * 2024-12-26 22:14:00 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-26 22:14:00 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-26 22:14:00 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-26 22:14:00 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-26 22:14:00 (9251) [INFO] compromise: * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-26 22:14:00 (9251) [INFO] * 2024-12-26 22:14:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-26 22:14: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-26 22:14:00 (9268) [INFO] * 2024-12-26 22:14: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-26 22:14: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-26 22:14:01 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-26 22:14:02 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dG0ySUfbVC/ea_profile.json * 2024-12-26 22:14: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/dG0ySUfbVC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-26 22:14:03 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-27 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-27 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-27 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-27 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-27 22:13:45 (9238) [INFO] * 2024-12-27 22:13:49 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-27 22:13:49 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-27 22:13:49 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-27 22:13:49 (9238) [INFO] * 2024-12-27 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-27 22:13:53 (9238) [INFO] * 2024-12-27 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 22:13:53 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-27 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-27 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-27 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-27 22:13:55 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-27 22:13: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-27 22:13:55 (9251) [INFO] Trying other mirror. * 2024-12-27 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-27 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-27 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-27 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-27 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-27 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-27 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-27 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-27 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2024-12-27 22:13:55 (9251) [INFO] or * 2024-12-27 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-27 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-27 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-27 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-27 22:13:55 (9251) [INFO] compromise: * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-27 22:13:55 (9251) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-27 22:13: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-27 22:13:55 (9268) [INFO] * 2024-12-27 22:13: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-27 22:13:55 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-27 22:13:55 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-27 22:13:55 (9238) [INFO] * 2024-12-27 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 22:13:55 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-27 22:13:55 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-27 22:13:55 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-27 22:13:55 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-27 22:13:55 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-27 22:13:55 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-27 22:13:55 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-27 22:13:55 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-27 22:13:55 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-27 22:13:55 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-27 22:13:55 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-27 22:13:55 (9268) [INFO] * 2024-12-27 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-27 22:13:55 (9238) [INFO] * 2024-12-27 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-27 22:13:56 (9251) [INFO] Determining fastest mirrors * 2024-12-27 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-27 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-27 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-27 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-27 22:13: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 22:13:58 (9251) [INFO] Trying other mirror. * 2024-12-27 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-27 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-27 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-27 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-27 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-27 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-27 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-27 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-27 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2024-12-27 22:13:58 (9251) [INFO] or * 2024-12-27 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-27 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-27 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-27 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-27 22:13:58 (9251) [INFO] compromise: * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-27 22:13:58 (9251) [INFO] * 2024-12-27 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-27 22:13: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 22:13:58 (9268) [INFO] * 2024-12-27 22:13: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 22:13: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 22:13:58 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-27 22:13:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qFnGFFcT2Z/ea_profile.json * 2024-12-27 22:14: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/qFnGFFcT2Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-27 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-28 22:14:30 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-28 22:14:31 (10313) [INFO] Script is up to date. * 2024-12-28 22:14:32 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-28 22:14:32 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-28 22:14:32 (9238) [INFO] * 2024-12-28 22:14:35 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-28 22:14:35 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-28 22:14:35 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-28 22:14:35 (9238) [INFO] * 2024-12-28 22:14:39 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-28 22:14:39 (9238) [INFO] * 2024-12-28 22:14:39 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 22:14:39 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-28 22:14:40 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-28 22:14:40 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-28 22:14:40 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-28 22:14:40 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-28 22:14: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 22:14:40 (9251) [INFO] Trying other mirror. * 2024-12-28 22:14:40 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-28 22:14:40 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-28 22:14:40 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-28 22:14:40 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-28 22:14:40 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-28 22:14:40 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-28 22:14:40 (9251) [INFO] yum --disablerepo=base ... * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-28 22:14:40 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-28 22:14:40 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] yum-config-manager --disable base * 2024-12-28 22:14:40 (9251) [INFO] or * 2024-12-28 22:14:40 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-28 22:14:40 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-28 22:14:40 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-28 22:14:40 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-28 22:14:40 (9251) [INFO] compromise: * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-28 22:14:40 (9251) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-28 22:14: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 22:14:40 (9268) [INFO] * 2024-12-28 22:14: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 22:14:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-28 22:14:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-28 22:14:40 (9238) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 22:14:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-28 22:14:40 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-28 22:14:40 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-28 22:14:40 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-28 22:14:40 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-28 22:14:40 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-28 22:14:40 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-28 22:14:40 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-28 22:14:40 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-28 22:14:40 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-28 22:14:40 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-28 22:14:40 (9268) [INFO] * 2024-12-28 22:14:40 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-28 22:14:40 (9238) [INFO] * 2024-12-28 22:14:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-28 22:14:40 (9251) [INFO] Determining fastest mirrors * 2024-12-28 22:14:42 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-28 22:14:42 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-28 22:14:42 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-28 22:14:42 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-28 22:14:43 (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 22:14:43 (9251) [INFO] Trying other mirror. * 2024-12-28 22:14:43 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-28 22:14:43 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-28 22:14:43 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-28 22:14:43 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-28 22:14:43 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-28 22:14:43 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-28 22:14:43 (9251) [INFO] yum --disablerepo=base ... * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-28 22:14:43 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-28 22:14:43 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] yum-config-manager --disable base * 2024-12-28 22:14:43 (9251) [INFO] or * 2024-12-28 22:14:43 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-28 22:14:43 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-28 22:14:43 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-28 22:14:43 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-28 22:14:43 (9251) [INFO] compromise: * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-28 22:14:43 (9251) [INFO] * 2024-12-28 22:14:43 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-28 22:14:43 (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 22:14:43 (9268) [INFO] * 2024-12-28 22:14:43 (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 22:14:43 (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 22:14:43 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-28 22:14:44 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CPzhZtvwVj/ea_profile.json * 2024-12-28 22:14:45 (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/CPzhZtvwVj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-28 22:14:45 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-29 22:14:35 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-29 22:14:36 (10313) [INFO] Script is up to date. * 2024-12-29 22:14:37 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-29 22:14:37 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-29 22:14:37 (9238) [INFO] * 2024-12-29 22:14:41 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-29 22:14:41 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-29 22:14:41 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-29 22:14:41 (9238) [INFO] * 2024-12-29 22:14:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-29 22:14:45 (9238) [INFO] * 2024-12-29 22:14:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 22:14:46 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-29 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-29 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-29 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-29 22:14:47 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2024-12-29 22:14: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-29 22:14:48 (9251) [INFO] Trying other mirror. * 2024-12-29 22:14:48 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-29 22:14:48 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-29 22:14:48 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-29 22:14:48 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-29 22:14:48 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-29 22:14:48 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-29 22:14:48 (9251) [INFO] yum --disablerepo=base ... * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-29 22:14:48 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-29 22:14:48 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] yum-config-manager --disable base * 2024-12-29 22:14:48 (9251) [INFO] or * 2024-12-29 22:14:48 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-29 22:14:48 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-29 22:14:48 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-29 22:14:48 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-29 22:14:48 (9251) [INFO] compromise: * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-29 22:14:48 (9251) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-29 22:14: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-29 22:14:48 (9268) [INFO] * 2024-12-29 22:14: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-29 22:14:48 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-29 22:14:48 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-29 22:14:48 (9238) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 22:14:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-29 22:14:48 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-29 22:14:48 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-29 22:14:48 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-29 22:14:48 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-29 22:14:48 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-29 22:14:48 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-29 22:14:48 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-29 22:14:48 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-29 22:14:48 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-29 22:14:48 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-29 22:14:48 (9268) [INFO] * 2024-12-29 22:14:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-29 22:14:48 (9238) [INFO] * 2024-12-29 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-29 22:14:48 (9251) [INFO] Determining fastest mirrors * 2024-12-29 22:14:51 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-29 22:14:51 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-29 22:14:51 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-29 22:14:51 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-29 22:14: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-29 22:14:51 (9251) [INFO] Trying other mirror. * 2024-12-29 22:14:51 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-29 22:14:51 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-29 22:14:51 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-29 22:14:51 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-29 22:14:51 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-29 22:14:51 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-29 22:14:51 (9251) [INFO] yum --disablerepo=base ... * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-29 22:14:51 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-29 22:14:51 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] yum-config-manager --disable base * 2024-12-29 22:14:51 (9251) [INFO] or * 2024-12-29 22:14:51 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-29 22:14:51 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-29 22:14:51 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-29 22:14:51 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-29 22:14:51 (9251) [INFO] compromise: * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-29 22:14:51 (9251) [INFO] * 2024-12-29 22:14:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-29 22:14: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-29 22:14:51 (9268) [INFO] * 2024-12-29 22:14: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-29 22:14: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-29 22:14:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-29 22:14:53 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ySk3wMse5Q/ea_profile.json * 2024-12-29 22:14: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/ySk3wMse5Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-29 22:14:55 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-30 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-30 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-30 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-30 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-30 22:13:45 (9238) [INFO] * 2024-12-30 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-30 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-30 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-30 22:13:51 (9238) [INFO] * 2024-12-30 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-30 22:13:56 (9238) [INFO] * 2024-12-30 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-30 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-30 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-30 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-30 22:13:57 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-30 22:13: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-30 22:13:57 (9251) [INFO] Trying other mirror. * 2024-12-30 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-30 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-30 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-30 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-30 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-30 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-30 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-30 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-30 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2024-12-30 22:13:57 (9251) [INFO] or * 2024-12-30 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-30 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-30 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-30 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-30 22:13:57 (9251) [INFO] compromise: * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-30 22:13:57 (9251) [INFO] * 2024-12-30 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-30 22:13: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-30 22:13:57 (9268) [INFO] * 2024-12-30 22:13:57 (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 22:13:57 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-30 22:13:57 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-30 22:13:57 (9238) [INFO] * 2024-12-30 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 22:13:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-30 22:13:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-30 22:13:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-30 22:13:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-30 22:13:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-30 22:13:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-30 22:13:58 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-30 22:13:58 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-30 22:13:58 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-30 22:13:58 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-30 22:13:58 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-30 22:13:58 (9268) [INFO] * 2024-12-30 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-30 22:13:58 (9238) [INFO] * 2024-12-30 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-30 22:13:58 (9251) [INFO] Determining fastest mirrors * 2024-12-30 22:13:59 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-30 22:13:59 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-30 22:13:59 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-30 22:13:59 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-30 22:13: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-30 22:13:59 (9251) [INFO] Trying other mirror. * 2024-12-30 22:13:59 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-30 22:13:59 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-30 22:13:59 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-30 22:13:59 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-30 22:13:59 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-30 22:13:59 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-30 22:13:59 (9251) [INFO] yum --disablerepo=base ... * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-30 22:13:59 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-30 22:13:59 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] yum-config-manager --disable base * 2024-12-30 22:13:59 (9251) [INFO] or * 2024-12-30 22:13:59 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-30 22:13:59 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-30 22:13:59 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-30 22:13:59 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-30 22:13:59 (9251) [INFO] compromise: * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-30 22:13:59 (9251) [INFO] * 2024-12-30 22:13:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-30 22:13: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-30 22:14:00 (9268) [INFO] * 2024-12-30 22:14: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-30 22:14: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-30 22:14:00 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-30 22:14:01 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/D2UFU2lEoW/ea_profile.json * 2024-12-30 22:14: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/D2UFU2lEoW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-30 22:14:03 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2024-12-31 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2024-12-31 22:13:44 (10313) [INFO] Script is up to date. * 2024-12-31 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2024-12-31 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2024-12-31 22:13:45 (9238) [INFO] * 2024-12-31 22:13:48 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2024-12-31 22:13:48 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2024-12-31 22:13:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2024-12-31 22:13:48 (9238) [INFO] * 2024-12-31 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-31 22:13:51 (9238) [INFO] * 2024-12-31 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2024-12-31 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-31 22:13:52 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-31 22:13:52 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-31 22:13:52 (9251) [INFO] * epel: mirrors.hostiserver.com * 2024-12-31 22:13: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-31 22:13:53 (9251) [INFO] Trying other mirror. * 2024-12-31 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-31 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-31 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-31 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-31 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-31 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-31 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-31 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-31 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2024-12-31 22:13:53 (9251) [INFO] or * 2024-12-31 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-31 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-31 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-31 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-31 22:13:53 (9251) [INFO] compromise: * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-31 22:13:53 (9251) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-31 22:13: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-31 22:13:53 (9268) [INFO] * 2024-12-31 22:13: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 * 2024-12-31 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2024-12-31 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2024-12-31 22:13:53 (9238) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 22:13:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2024-12-31 22:13:53 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2024-12-31 22:13:53 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2024-12-31 22:13:53 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2024-12-31 22:13:53 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2024-12-31 22:13:53 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2024-12-31 22:13:53 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2024-12-31 22:13:53 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2024-12-31 22:13:53 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2024-12-31 22:13:53 (9251) [INFO] Cleaning up list of fastest mirrors * 2024-12-31 22:13:53 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2024-12-31 22:13:53 (9268) [INFO] * 2024-12-31 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2024-12-31 22:13:53 (9238) [INFO] * 2024-12-31 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2024-12-31 22:13:53 (9251) [INFO] Determining fastest mirrors * 2024-12-31 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2024-12-31 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2024-12-31 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2024-12-31 22:13:55 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2024-12-31 22:13: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-31 22:13:55 (9251) [INFO] Trying other mirror. * 2024-12-31 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2024-12-31 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2024-12-31 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2024-12-31 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2024-12-31 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2024-12-31 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2024-12-31 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2024-12-31 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2024-12-31 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2024-12-31 22:13:55 (9251) [INFO] or * 2024-12-31 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2024-12-31 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2024-12-31 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2024-12-31 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2024-12-31 22:13:55 (9251) [INFO] compromise: * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2024-12-31 22:13:55 (9251) [INFO] * 2024-12-31 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2024-12-31 22:13: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-31 22:13:55 (9268) [INFO] * 2024-12-31 22:13: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-31 22:13: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-31 22:13:55 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2024-12-31 22:13:56 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B4SA4PN7I0/ea_profile.json * 2024-12-31 22:13: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/B4SA4PN7I0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2024-12-31 22:13:57 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-01 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-01 22:13:46 (10313) [INFO] Script is up to date. * 2025-01-01 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-01 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-01 22:13:48 (9238) [INFO] * 2025-01-01 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-01 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-01 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-01 22:13:51 (9238) [INFO] * 2025-01-01 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-01 22:13:55 (9238) [INFO] * 2025-01-01 22:13:55 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 22:13:55 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-01 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-01 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-01 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-01 22:13:56 (9251) [INFO] * epel: mirror.math.princeton.edu * 2025-01-01 22:13: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 22:13:56 (9251) [INFO] Trying other mirror. * 2025-01-01 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-01 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-01 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-01 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-01 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-01 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-01 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-01 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-01 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2025-01-01 22:13:56 (9251) [INFO] or * 2025-01-01 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-01 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-01 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-01 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-01 22:13:56 (9251) [INFO] compromise: * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-01 22:13:56 (9251) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-01 22:13: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 22:13:56 (9268) [INFO] * 2025-01-01 22:13: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 * 2025-01-01 22:13:56 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-01 22:13:56 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-01 22:13:56 (9238) [INFO] * 2025-01-01 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 22:13:56 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-01 22:13:56 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-01 22:13:56 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-01 22:13:56 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-01 22:13:56 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-01 22:13:56 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-01 22:13:56 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-01 22:13:56 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-01 22:13:56 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-01 22:13:56 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-01 22:13:56 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-01 22:13:56 (9268) [INFO] * 2025-01-01 22:13:56 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-01 22:13:56 (9238) [INFO] * 2025-01-01 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-01 22:13:57 (9251) [INFO] Determining fastest mirrors * 2025-01-01 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-01 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-01 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-01 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-01 22:13: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-01 22:13:58 (9251) [INFO] Trying other mirror. * 2025-01-01 22:13:58 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-01 22:13:58 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-01 22:13:58 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-01 22:13:58 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-01 22:13:58 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-01 22:13:58 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-01 22:13:58 (9251) [INFO] yum --disablerepo=base ... * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-01 22:13:58 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-01 22:13:58 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] yum-config-manager --disable base * 2025-01-01 22:13:58 (9251) [INFO] or * 2025-01-01 22:13:58 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-01 22:13:58 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-01 22:13:58 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-01 22:13:58 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-01 22:13:58 (9251) [INFO] compromise: * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-01 22:13:58 (9251) [INFO] * 2025-01-01 22:13:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-01 22:13: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-01 22:13:58 (9268) [INFO] * 2025-01-01 22:13: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-01 22:13: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-01 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-01 22:13:59 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UmXKgj6ya3/ea_profile.json * 2025-01-01 22:14: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/UmXKgj6ya3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-01 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-02 22:13:40 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-02 22:13:40 (10313) [INFO] Script is up to date. * 2025-01-02 22:13:41 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-02 22:13:41 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-02 22:13:41 (9238) [INFO] * 2025-01-02 22:13:44 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-02 22:13:44 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-02 22:13:44 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-02 22:13:44 (9238) [INFO] * 2025-01-02 22:13:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-02 22:13:48 (9238) [INFO] * 2025-01-02 22:13:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 22:13:48 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-02 22:13:49 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-02 22:13:49 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-02 22:13:49 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-02 22:13:49 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-02 22:13: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-02 22:13:49 (9251) [INFO] Trying other mirror. * 2025-01-02 22:13:49 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-02 22:13:49 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-02 22:13:49 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-02 22:13:49 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-02 22:13:49 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-02 22:13:49 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-02 22:13:49 (9251) [INFO] yum --disablerepo=base ... * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-02 22:13:49 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-02 22:13:49 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] yum-config-manager --disable base * 2025-01-02 22:13:49 (9251) [INFO] or * 2025-01-02 22:13:49 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-02 22:13:49 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-02 22:13:49 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-02 22:13:49 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-02 22:13:49 (9251) [INFO] compromise: * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-02 22:13:49 (9251) [INFO] * 2025-01-02 22:13:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-02 22:13: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-02 22:13:50 (9268) [INFO] * 2025-01-02 22:13:50 (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 22:13:50 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-02 22:13:50 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-02 22:13:50 (9238) [INFO] * 2025-01-02 22:13:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 22:13:50 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-02 22:13:50 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-02 22:13:50 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-02 22:13:50 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-02 22:13:50 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-02 22:13:50 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-02 22:13:50 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-02 22:13:50 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-02 22:13:50 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-02 22:13:50 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-02 22:13:50 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-02 22:13:50 (9268) [INFO] * 2025-01-02 22:13:50 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-02 22:13:50 (9238) [INFO] * 2025-01-02 22:13:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-02 22:13:50 (9251) [INFO] Determining fastest mirrors * 2025-01-02 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-02 22:13:52 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-02 22:13:52 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-02 22:13:52 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-02 22:13: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-02 22:13:52 (9251) [INFO] Trying other mirror. * 2025-01-02 22:13:52 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-02 22:13:52 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-02 22:13:52 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-02 22:13:52 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-02 22:13:52 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-02 22:13:52 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-02 22:13:52 (9251) [INFO] yum --disablerepo=base ... * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-02 22:13:52 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-02 22:13:52 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] yum-config-manager --disable base * 2025-01-02 22:13:52 (9251) [INFO] or * 2025-01-02 22:13:52 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-02 22:13:52 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-02 22:13:52 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-02 22:13:52 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-02 22:13:52 (9251) [INFO] compromise: * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-02 22:13:52 (9251) [INFO] * 2025-01-02 22:13:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-02 22:13: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-02 22:13:52 (9268) [INFO] * 2025-01-02 22:13:52 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-02 22:13:52 (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 22:13:52 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-02 22:13:53 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WWgfL0am9p/ea_profile.json * 2025-01-02 22:13: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/WWgfL0am9p/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-02 22:13:54 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-03 22:13:41 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-03 22:13:41 (10313) [INFO] Script is up to date. * 2025-01-03 22:13:42 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-03 22:13:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-03 22:13:42 (9238) [INFO] * 2025-01-03 22:13:46 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-03 22:13:46 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-03 22:13:46 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-03 22:13:46 (9238) [INFO] * 2025-01-03 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-03 22:13:51 (9238) [INFO] * 2025-01-03 22:13:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 22:13:51 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-03 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-03 22:13:52 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-03 22:13:52 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-03 22:13:52 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-03 22:13: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-03 22:13:52 (9251) [INFO] Trying other mirror. * 2025-01-03 22:13:52 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-03 22:13:52 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-03 22:13:52 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-03 22:13:52 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-03 22:13:52 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-03 22:13:52 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-03 22:13:52 (9251) [INFO] yum --disablerepo=base ... * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-03 22:13:52 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-03 22:13:52 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] yum-config-manager --disable base * 2025-01-03 22:13:52 (9251) [INFO] or * 2025-01-03 22:13:52 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-03 22:13:52 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-03 22:13:52 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-03 22:13:52 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-03 22:13:52 (9251) [INFO] compromise: * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-03 22:13:52 (9251) [INFO] * 2025-01-03 22:13:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-03 22:13: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-03 22:13:52 (9268) [INFO] * 2025-01-03 22:13: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-03 22:13:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-03 22:13:52 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-03 22:13:52 (9238) [INFO] * 2025-01-03 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 22:13:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-03 22:13:53 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-03 22:13:53 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-03 22:13:53 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-03 22:13:53 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-03 22:13:53 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-03 22:13:53 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-03 22:13:53 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-03 22:13:53 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-03 22:13:53 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-03 22:13:53 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-03 22:13:53 (9268) [INFO] * 2025-01-03 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-03 22:13:53 (9238) [INFO] * 2025-01-03 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-03 22:13:53 (9251) [INFO] Determining fastest mirrors * 2025-01-03 22:13:54 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-03 22:13:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-03 22:13:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-03 22:13:54 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-03 22:13: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-03 22:13:55 (9251) [INFO] Trying other mirror. * 2025-01-03 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-03 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-03 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-03 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-03 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-03 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-03 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-03 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-03 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2025-01-03 22:13:55 (9251) [INFO] or * 2025-01-03 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-03 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-03 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-03 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-03 22:13:55 (9251) [INFO] compromise: * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-03 22:13:55 (9251) [INFO] * 2025-01-03 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-03 22:13: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-03 22:13:55 (9268) [INFO] * 2025-01-03 22:13:55 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-03 22:13: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 * 2025-01-03 22:13:55 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-03 22:13:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dk4SgXCQZQ/ea_profile.json * 2025-01-03 22:13: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/dk4SgXCQZQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-03 22:13:58 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-04 22:14:35 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-04 22:14:35 (10313) [INFO] Script is up to date. * 2025-01-04 22:14:37 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-04 22:14:37 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-04 22:14:37 (9238) [INFO] * 2025-01-04 22:14:41 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-04 22:14:41 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-04 22:14:41 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-04 22:14:41 (9238) [INFO] * 2025-01-04 22:14:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-04 22:14:45 (9238) [INFO] * 2025-01-04 22:14:45 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 22:14:45 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-04 22:14:46 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-04 22:14:46 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-04 22:14:46 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-04 22:14:46 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-04 22:14: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-04 22:14:46 (9251) [INFO] Trying other mirror. * 2025-01-04 22:14:46 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-04 22:14:46 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-04 22:14:46 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-04 22:14:46 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-04 22:14:46 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-04 22:14:46 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-04 22:14:46 (9251) [INFO] yum --disablerepo=base ... * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-04 22:14:46 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-04 22:14:46 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] yum-config-manager --disable base * 2025-01-04 22:14:46 (9251) [INFO] or * 2025-01-04 22:14:46 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-04 22:14:46 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-04 22:14:46 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-04 22:14:46 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-04 22:14:46 (9251) [INFO] compromise: * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-04 22:14:46 (9251) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-04 22:14: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-04 22:14:46 (9268) [INFO] * 2025-01-04 22:14: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-04 22:14:46 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-04 22:14:46 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-04 22:14:46 (9238) [INFO] * 2025-01-04 22:14:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 22:14:46 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-04 22:14:46 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-04 22:14:46 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-04 22:14:46 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-04 22:14:46 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-04 22:14:46 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-04 22:14:46 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-04 22:14:46 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-04 22:14:46 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-04 22:14:46 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-04 22:14:46 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-04 22:14:46 (9268) [INFO] * 2025-01-04 22:14:46 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-04 22:14:46 (9238) [INFO] * 2025-01-04 22:14:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-04 22:14:47 (9251) [INFO] Determining fastest mirrors * 2025-01-04 22:14:48 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-04 22:14:48 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-04 22:14:48 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-04 22:14:48 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-04 22:14: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-04 22:14:48 (9251) [INFO] Trying other mirror. * 2025-01-04 22:14:48 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-04 22:14:48 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-04 22:14:48 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-04 22:14:48 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-04 22:14:48 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-04 22:14:48 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-04 22:14:48 (9251) [INFO] yum --disablerepo=base ... * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-04 22:14:48 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-04 22:14:48 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] yum-config-manager --disable base * 2025-01-04 22:14:48 (9251) [INFO] or * 2025-01-04 22:14:48 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-04 22:14:48 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-04 22:14:48 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-04 22:14:48 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-04 22:14:48 (9251) [INFO] compromise: * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-04 22:14:48 (9251) [INFO] * 2025-01-04 22:14:48 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-04 22:14: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-04 22:14:48 (9268) [INFO] * 2025-01-04 22:14:48 (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 22:14:48 (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 22:14:49 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-04 22:14:49 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NQhKvvC00H/ea_profile.json * 2025-01-04 22:14:51 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NQhKvvC00H/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-04 22:14:51 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-05 22:14:30 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-05 22:14:30 (10313) [INFO] Script is up to date. * 2025-01-05 22:14:31 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-05 22:14:31 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-05 22:14:31 (9238) [INFO] * 2025-01-05 22:14:34 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-05 22:14:34 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-05 22:14:34 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-05 22:14:34 (9238) [INFO] * 2025-01-05 22:14:38 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-05 22:14:38 (9238) [INFO] * 2025-01-05 22:14:38 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 22:14:38 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-05 22:14:40 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-05 22:14:40 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-05 22:14:40 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-05 22:14:40 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-01-05 22:14: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 * 2025-01-05 22:14:40 (9251) [INFO] Trying other mirror. * 2025-01-05 22:14:40 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-05 22:14:40 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-05 22:14:40 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-05 22:14:40 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-05 22:14:40 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-05 22:14:40 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-05 22:14:40 (9251) [INFO] yum --disablerepo=base ... * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-05 22:14:40 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-05 22:14:40 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] yum-config-manager --disable base * 2025-01-05 22:14:40 (9251) [INFO] or * 2025-01-05 22:14:40 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-05 22:14:40 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-05 22:14:40 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-05 22:14:40 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-05 22:14:40 (9251) [INFO] compromise: * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-05 22:14:40 (9251) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-05 22:14: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 * 2025-01-05 22:14:40 (9268) [INFO] * 2025-01-05 22:14: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 * 2025-01-05 22:14:40 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-05 22:14:40 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-05 22:14:40 (9238) [INFO] * 2025-01-05 22:14:40 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 22:14:40 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-05 22:14:40 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-05 22:14:40 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-05 22:14:40 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-05 22:14:40 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-05 22:14:40 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-05 22:14:40 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-05 22:14:40 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-05 22:14:40 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-05 22:14:40 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-05 22:14:41 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-05 22:14:41 (9268) [INFO] * 2025-01-05 22:14:41 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-05 22:14:41 (9238) [INFO] * 2025-01-05 22:14:41 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-05 22:14:41 (9251) [INFO] Determining fastest mirrors * 2025-01-05 22:14:43 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-05 22:14:43 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-05 22:14:43 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-05 22:14:43 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-05 22:14:43 (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 22:14:43 (9251) [INFO] Trying other mirror. * 2025-01-05 22:14:43 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-05 22:14:43 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-05 22:14:43 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-05 22:14:43 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-05 22:14:43 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-05 22:14:43 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-05 22:14:43 (9251) [INFO] yum --disablerepo=base ... * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-05 22:14:43 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-05 22:14:43 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] yum-config-manager --disable base * 2025-01-05 22:14:43 (9251) [INFO] or * 2025-01-05 22:14:43 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-05 22:14:43 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-05 22:14:43 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-05 22:14:43 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-05 22:14:43 (9251) [INFO] compromise: * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-05 22:14:43 (9251) [INFO] * 2025-01-05 22:14:43 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-05 22:14:43 (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 22:14:43 (9268) [INFO] * 2025-01-05 22:14:43 (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 22:14:43 (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 22:14:44 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-05 22:14:44 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kaArv5neAv/ea_profile.json * 2025-01-05 22:14: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/kaArv5neAv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-05 22:14:47 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-06 22:13:46 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-06 22:13:46 (10313) [INFO] Script is up to date. * 2025-01-06 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-06 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-06 22:13:48 (9238) [INFO] * 2025-01-06 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-06 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-06 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-06 22:13:51 (9238) [INFO] * 2025-01-06 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-06 22:13:55 (9238) [INFO] * 2025-01-06 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-06 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-06 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-06 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-06 22:13:56 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-01-06 22:13: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-06 22:13:57 (9251) [INFO] Trying other mirror. * 2025-01-06 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-06 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-06 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-06 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-06 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-06 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-06 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-06 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-06 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2025-01-06 22:13:57 (9251) [INFO] or * 2025-01-06 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-06 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-06 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-06 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-06 22:13:57 (9251) [INFO] compromise: * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-06 22:13:57 (9251) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-06 22:13: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-06 22:13:57 (9268) [INFO] * 2025-01-06 22:13:57 (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 22:13:57 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-06 22:13:57 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-06 22:13:57 (9238) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 22:13:57 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-06 22:13:57 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-06 22:13:57 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-06 22:13:57 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-06 22:13:57 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-06 22:13:57 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-06 22:13:57 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-06 22:13:57 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-06 22:13:57 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-06 22:13:57 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-06 22:13:57 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-06 22:13:57 (9268) [INFO] * 2025-01-06 22:13:57 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-06 22:13:57 (9238) [INFO] * 2025-01-06 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-06 22:13:57 (9251) [INFO] Determining fastest mirrors * 2025-01-06 22:13:58 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-06 22:13:58 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-06 22:13:58 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-06 22:13:58 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-06 22:13: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 22:13:59 (9251) [INFO] Trying other mirror. * 2025-01-06 22:13:59 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-06 22:13:59 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-06 22:13:59 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-06 22:13:59 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-06 22:13:59 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-06 22:13:59 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-06 22:13:59 (9251) [INFO] yum --disablerepo=base ... * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-06 22:13:59 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-06 22:13:59 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] yum-config-manager --disable base * 2025-01-06 22:13:59 (9251) [INFO] or * 2025-01-06 22:13:59 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-06 22:13:59 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-06 22:13:59 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-06 22:13:59 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-06 22:13:59 (9251) [INFO] compromise: * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-06 22:13:59 (9251) [INFO] * 2025-01-06 22:13:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-06 22:13: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 22:13:59 (9268) [INFO] * 2025-01-06 22:13: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 22:13: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 22:13:59 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-06 22:14:00 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pP9fV0H4SR/ea_profile.json * 2025-01-06 22:14: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/pP9fV0H4SR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-06 22:14:01 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-07 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-07 22:13:44 (10313) [INFO] Script is up to date. * 2025-01-07 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-07 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-07 22:13:45 (9238) [INFO] * 2025-01-07 22:13:48 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-07 22:13:48 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-07 22:13:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-07 22:13:48 (9238) [INFO] * 2025-01-07 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-07 22:13:52 (9238) [INFO] * 2025-01-07 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-07 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-07 22:13:53 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-07 22:13:53 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-07 22:13:53 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-07 22:13: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-07 22:13:53 (9251) [INFO] Trying other mirror. * 2025-01-07 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-07 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-07 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-07 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-07 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-07 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-07 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-07 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-07 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2025-01-07 22:13:53 (9251) [INFO] or * 2025-01-07 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-07 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-07 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-07 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-07 22:13:53 (9251) [INFO] compromise: * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-07 22:13:53 (9251) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-07 22:13: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-07 22:13:53 (9268) [INFO] * 2025-01-07 22:13: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-07 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-07 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-07 22:13:53 (9238) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 22:13:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-07 22:13:53 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-07 22:13:53 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-07 22:13:53 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-07 22:13:53 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-07 22:13:53 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-07 22:13:53 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-07 22:13:53 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-07 22:13:53 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-07 22:13:53 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-07 22:13:53 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-07 22:13:53 (9268) [INFO] * 2025-01-07 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-07 22:13:53 (9238) [INFO] * 2025-01-07 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-07 22:13:54 (9251) [INFO] Determining fastest mirrors * 2025-01-07 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-07 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-07 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-07 22:13:55 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-07 22:13: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-07 22:13:55 (9251) [INFO] Trying other mirror. * 2025-01-07 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-07 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-07 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-07 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-07 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-07 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-07 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-07 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-07 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2025-01-07 22:13:55 (9251) [INFO] or * 2025-01-07 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-07 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-07 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-07 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-07 22:13:55 (9251) [INFO] compromise: * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-07 22:13:55 (9251) [INFO] * 2025-01-07 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-07 22:13: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-07 22:13:55 (9268) [INFO] * 2025-01-07 22:13:55 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-07 22:13: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 * 2025-01-07 22:13:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-07 22:13:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_a91FTZDDW/ea_profile.json * 2025-01-07 22:13: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/_a91FTZDDW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-07 22:13:58 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-08 22:13:47 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-08 22:13:47 (10313) [INFO] Script is up to date. * 2025-01-08 22:13:48 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-08 22:13:48 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-08 22:13:48 (9238) [INFO] * 2025-01-08 22:13:51 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-08 22:13:51 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-08 22:13:51 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-08 22:13:51 (9238) [INFO] * 2025-01-08 22:13:57 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-08 22:13:57 (9238) [INFO] * 2025-01-08 22:13:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 22:13:58 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-08 22:13:59 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-08 22:13:59 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-08 22:13:59 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-08 22:13:59 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-08 22:13: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-08 22:13:59 (9251) [INFO] Trying other mirror. * 2025-01-08 22:13:59 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-08 22:13:59 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-08 22:13:59 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-08 22:13:59 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-08 22:13:59 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-08 22:13:59 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-08 22:13:59 (9251) [INFO] yum --disablerepo=base ... * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-08 22:13:59 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-08 22:13:59 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] yum-config-manager --disable base * 2025-01-08 22:13:59 (9251) [INFO] or * 2025-01-08 22:13:59 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-08 22:13:59 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-08 22:13:59 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-08 22:13:59 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-08 22:13:59 (9251) [INFO] compromise: * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-08 22:13:59 (9251) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-08 22:13: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-08 22:13:59 (9268) [INFO] * 2025-01-08 22:13: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 * 2025-01-08 22:13:59 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-08 22:13:59 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-08 22:13:59 (9238) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 22:13:59 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-08 22:13:59 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-08 22:13:59 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-08 22:13:59 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-08 22:13:59 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-08 22:13:59 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-08 22:13:59 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-08 22:13:59 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-08 22:13:59 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-08 22:13:59 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-08 22:13:59 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-08 22:13:59 (9268) [INFO] * 2025-01-08 22:13:59 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-08 22:13:59 (9238) [INFO] * 2025-01-08 22:13:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-08 22:14:00 (9251) [INFO] Determining fastest mirrors * 2025-01-08 22:14:01 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-08 22:14:01 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-08 22:14:01 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-08 22:14:01 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-08 22:14: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 * 2025-01-08 22:14:01 (9251) [INFO] Trying other mirror. * 2025-01-08 22:14:01 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-08 22:14:01 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-08 22:14:01 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-08 22:14:01 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-08 22:14:01 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-08 22:14:01 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-08 22:14:01 (9251) [INFO] yum --disablerepo=base ... * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-08 22:14:01 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-08 22:14:01 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] yum-config-manager --disable base * 2025-01-08 22:14:01 (9251) [INFO] or * 2025-01-08 22:14:01 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-08 22:14:01 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-08 22:14:01 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-08 22:14:01 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-08 22:14:01 (9251) [INFO] compromise: * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-08 22:14:01 (9251) [INFO] * 2025-01-08 22:14:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-08 22:14: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 * 2025-01-08 22:14:01 (9268) [INFO] * 2025-01-08 22:14:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-08 22:14:01 (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 22:14:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-08 22:14:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UUc2twZhmh/ea_profile.json * 2025-01-08 22:14: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/UUc2twZhmh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-08 22:14:04 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-09 22:13:41 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-09 22:13:41 (10313) [INFO] Script is up to date. * 2025-01-09 22:13:42 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-09 22:13:42 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-09 22:13:42 (9238) [INFO] * 2025-01-09 22:13:46 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-09 22:13:46 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-09 22:13:46 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-09 22:13:46 (9238) [INFO] * 2025-01-09 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-09 22:13:51 (9238) [INFO] * 2025-01-09 22:13:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 22:13:51 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-09 22:13:52 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-09 22:13:52 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-09 22:13:52 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-09 22:13:52 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-09 22:13: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-09 22:13:52 (9251) [INFO] Trying other mirror. * 2025-01-09 22:13:52 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-09 22:13:52 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-09 22:13:52 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-09 22:13:52 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-09 22:13:52 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-09 22:13:52 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-09 22:13:52 (9251) [INFO] yum --disablerepo=base ... * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-09 22:13:52 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-09 22:13:52 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] yum-config-manager --disable base * 2025-01-09 22:13:52 (9251) [INFO] or * 2025-01-09 22:13:52 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-09 22:13:52 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-09 22:13:52 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-09 22:13:52 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-09 22:13:52 (9251) [INFO] compromise: * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-09 22:13:52 (9251) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-09 22:13: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-09 22:13:52 (9268) [INFO] * 2025-01-09 22:13: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-09 22:13:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-09 22:13:52 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-09 22:13:52 (9238) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 22:13:52 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-09 22:13:52 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-09 22:13:52 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-09 22:13:52 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-09 22:13:52 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-09 22:13:52 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-09 22:13:52 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-09 22:13:52 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-09 22:13:52 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-09 22:13:52 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-09 22:13:52 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-09 22:13:52 (9268) [INFO] * 2025-01-09 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-09 22:13:52 (9238) [INFO] * 2025-01-09 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-09 22:13:53 (9251) [INFO] Determining fastest mirrors * 2025-01-09 22:13:54 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-09 22:13:54 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-09 22:13:54 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-09 22:13:54 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-09 22:13: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-09 22:13:54 (9251) [INFO] Trying other mirror. * 2025-01-09 22:13:54 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-09 22:13:54 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-09 22:13:54 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-09 22:13:54 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-09 22:13:54 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-09 22:13:54 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-09 22:13:54 (9251) [INFO] yum --disablerepo=base ... * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-09 22:13:54 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-09 22:13:54 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] yum-config-manager --disable base * 2025-01-09 22:13:54 (9251) [INFO] or * 2025-01-09 22:13:54 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-09 22:13:54 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-09 22:13:54 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-09 22:13:54 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-09 22:13:54 (9251) [INFO] compromise: * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-09 22:13:54 (9251) [INFO] * 2025-01-09 22:13:54 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-09 22:13: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-09 22:13:54 (9268) [INFO] * 2025-01-09 22:13: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-09 22:13: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-09 22:13:54 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-09 22:13:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pRp3xrqJHM/ea_profile.json * 2025-01-09 22:13: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/pRp3xrqJHM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-09 22:13:56 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-10 22:13:43 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-10 22:13:44 (10313) [INFO] Script is up to date. * 2025-01-10 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-10 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-10 22:13:45 (9238) [INFO] * 2025-01-10 22:13:47 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-10 22:13:47 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-10 22:13:47 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-10 22:13:47 (9238) [INFO] * 2025-01-10 22:13:51 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-10 22:13:51 (9238) [INFO] * 2025-01-10 22:13:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-10 22:13:53 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-10 22:13:53 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-10 22:13:53 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-10 22:13:53 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-10 22:13: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-10 22:13:53 (9251) [INFO] Trying other mirror. * 2025-01-10 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-10 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-10 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-10 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-10 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-10 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-10 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-10 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-10 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2025-01-10 22:13:53 (9251) [INFO] or * 2025-01-10 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-10 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-10 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-10 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-10 22:13:53 (9251) [INFO] compromise: * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-10 22:13:53 (9251) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-10 22:13: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-10 22:13:53 (9268) [INFO] * 2025-01-10 22:13: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-10 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-10 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-10 22:13:53 (9238) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 22:13:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-10 22:13:53 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-10 22:13:53 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-10 22:13:53 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-10 22:13:53 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-10 22:13:53 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-10 22:13:53 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-10 22:13:53 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-10 22:13:53 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-10 22:13:53 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-10 22:13:53 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-10 22:13:53 (9268) [INFO] * 2025-01-10 22:13:53 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-10 22:13:53 (9238) [INFO] * 2025-01-10 22:13:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-10 22:13:54 (9251) [INFO] Determining fastest mirrors * 2025-01-10 22:13:55 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-10 22:13:55 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-10 22:13:55 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-10 22:13:55 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-10 22:13: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-10 22:13:55 (9251) [INFO] Trying other mirror. * 2025-01-10 22:13:55 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-10 22:13:55 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-10 22:13:55 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-10 22:13:55 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-10 22:13:55 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-10 22:13:55 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-10 22:13:55 (9251) [INFO] yum --disablerepo=base ... * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-10 22:13:55 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-10 22:13:55 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] yum-config-manager --disable base * 2025-01-10 22:13:55 (9251) [INFO] or * 2025-01-10 22:13:55 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-10 22:13:55 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-10 22:13:55 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-10 22:13:55 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-10 22:13:55 (9251) [INFO] compromise: * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-10 22:13:55 (9251) [INFO] * 2025-01-10 22:13:55 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-10 22:13: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-10 22:13:55 (9268) [INFO] * 2025-01-10 22:13:55 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-10 22:13: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 * 2025-01-10 22:13:55 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-10 22:13:56 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R5BcKOihOO/ea_profile.json * 2025-01-10 22:13: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/R5BcKOihOO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-10 22:13:58 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-11 22:14:33 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-11 22:14:33 (10313) [INFO] Script is up to date. * 2025-01-11 22:14:35 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-11 22:14:35 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-11 22:14:35 (9238) [INFO] * 2025-01-11 22:14:41 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-11 22:14:41 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-11 22:14:41 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-11 22:14:41 (9238) [INFO] * 2025-01-11 22:14:45 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-11 22:14:45 (9238) [INFO] * 2025-01-11 22:14:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 22:14:46 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-11 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-11 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-11 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-11 22:14:47 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-11 22:14: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-11 22:14:47 (9251) [INFO] Trying other mirror. * 2025-01-11 22:14:47 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-11 22:14:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-11 22:14:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-11 22:14:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-11 22:14:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-11 22:14:47 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-11 22:14:47 (9251) [INFO] yum --disablerepo=base ... * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-11 22:14:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-11 22:14:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] yum-config-manager --disable base * 2025-01-11 22:14:47 (9251) [INFO] or * 2025-01-11 22:14:47 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-11 22:14:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-11 22:14:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-11 22:14:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-11 22:14:47 (9251) [INFO] compromise: * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-11 22:14:47 (9251) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-11 22:14: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-11 22:14:47 (9268) [INFO] * 2025-01-11 22:14: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-11 22:14:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-11 22:14:47 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-11 22:14:47 (9238) [INFO] * 2025-01-11 22:14:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 22:14:47 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-11 22:14:47 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-11 22:14:47 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-11 22:14:47 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-11 22:14:47 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-11 22:14:47 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-11 22:14:47 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-11 22:14:47 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-11 22:14:47 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-11 22:14:47 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-11 22:14:47 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-11 22:14:47 (9268) [INFO] * 2025-01-11 22:14:47 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-11 22:14:47 (9238) [INFO] * 2025-01-11 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-11 22:14:48 (9251) [INFO] Determining fastest mirrors * 2025-01-11 22:14:51 (9251) [INFO] * EA4: 185.90.57.221 * 2025-01-11 22:14:51 (9251) [INFO] * cpanel-addons-production-feed: 185.90.57.221 * 2025-01-11 22:14:51 (9251) [INFO] * cpanel-plugins: 185.90.57.221 * 2025-01-11 22:14:51 (9251) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-01-11 22:14: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-11 22:14:51 (9251) [INFO] Trying other mirror. * 2025-01-11 22:14:51 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-11 22:14:51 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-11 22:14:51 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-11 22:14:51 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-11 22:14:51 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-11 22:14:51 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-11 22:14:51 (9251) [INFO] yum --disablerepo=base ... * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-11 22:14:51 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-11 22:14:51 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] yum-config-manager --disable base * 2025-01-11 22:14:51 (9251) [INFO] or * 2025-01-11 22:14:51 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-11 22:14:51 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-11 22:14:51 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-11 22:14:51 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-11 22:14:51 (9251) [INFO] compromise: * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-11 22:14:51 (9251) [INFO] * 2025-01-11 22:14:51 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-11 22:14: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-11 22:14:51 (9268) [INFO] * 2025-01-11 22:14: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-11 22:14: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-11 22:14:51 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-11 22:14:52 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Up97AW573y/ea_profile.json * 2025-01-11 22:14: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/Up97AW573y/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-11 22:14:54 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-12 22:14:37 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-12 22:14:37 (10313) [INFO] Script is up to date. * 2025-01-12 22:14:38 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-12 22:14:38 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-12 22:14:38 (9238) [INFO] * 2025-01-12 22:14:42 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-12 22:14:42 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-12 22:14:42 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-12 22:14:42 (9238) [INFO] * 2025-01-12 22:14:46 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-12 22:14:46 (9238) [INFO] * 2025-01-12 22:14:46 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 22:14:46 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-12 22:14:47 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-12 22:14:47 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-12 22:14:47 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-12 22:14:47 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-12 22:14: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-12 22:14:47 (9251) [INFO] Trying other mirror. * 2025-01-12 22:14:47 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-12 22:14:47 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-12 22:14:47 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-12 22:14:47 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-12 22:14:47 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-12 22:14:47 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-12 22:14:47 (9251) [INFO] yum --disablerepo=base ... * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-12 22:14:47 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-12 22:14:47 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] yum-config-manager --disable base * 2025-01-12 22:14:47 (9251) [INFO] or * 2025-01-12 22:14:47 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-12 22:14:47 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-12 22:14:47 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-12 22:14:47 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-12 22:14:47 (9251) [INFO] compromise: * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-12 22:14:47 (9251) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-12 22:14: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-12 22:14:47 (9268) [INFO] * 2025-01-12 22:14: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-12 22:14:47 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-12 22:14:47 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-12 22:14:47 (9238) [INFO] * 2025-01-12 22:14:47 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 22:14:48 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-12 22:14:48 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-12 22:14:48 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-12 22:14:48 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-12 22:14:48 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-12 22:14:48 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-12 22:14:48 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-12 22:14:48 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-12 22:14:48 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-12 22:14:48 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-12 22:14:48 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-12 22:14:48 (9268) [INFO] * 2025-01-12 22:14:48 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-12 22:14:48 (9238) [INFO] * 2025-01-12 22:14:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-12 22:14:48 (9251) [INFO] Determining fastest mirrors * 2025-01-12 22:14:49 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-12 22:14:49 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-12 22:14:49 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-12 22:14:49 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-12 22:14: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 * 2025-01-12 22:14:50 (9251) [INFO] Trying other mirror. * 2025-01-12 22:14:50 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-12 22:14:50 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-12 22:14:50 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-12 22:14:50 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-12 22:14:50 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-12 22:14:50 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-12 22:14:50 (9251) [INFO] yum --disablerepo=base ... * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-12 22:14:50 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-12 22:14:50 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] yum-config-manager --disable base * 2025-01-12 22:14:50 (9251) [INFO] or * 2025-01-12 22:14:50 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-12 22:14:50 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-12 22:14:50 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-12 22:14:50 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-12 22:14:50 (9251) [INFO] compromise: * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-12 22:14:50 (9251) [INFO] * 2025-01-12 22:14:50 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-12 22:14: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 * 2025-01-12 22:14:50 (9268) [INFO] * 2025-01-12 22:14:50 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-12 22:14: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 * 2025-01-12 22:14:50 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-12 22:14:51 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7NVNf3Fz0/ea_profile.json * 2025-01-12 22:14:52 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v7NVNf3Fz0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-12 22:14:52 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-13 22:13:44 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-13 22:13:44 (10313) [INFO] Script is up to date. * 2025-01-13 22:13:45 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-13 22:13:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-13 22:13:45 (9238) [INFO] * 2025-01-13 22:13:48 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-13 22:13:48 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-13 22:13:48 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-13 22:13:48 (9238) [INFO] * 2025-01-13 22:13:55 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-13 22:13:55 (9238) [INFO] * 2025-01-13 22:13:56 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 22:13:56 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-13 22:13:57 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-13 22:13:57 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-13 22:13:57 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-13 22:13:57 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-13 22:13: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-13 22:13:57 (9251) [INFO] Trying other mirror. * 2025-01-13 22:13:57 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-13 22:13:57 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-13 22:13:57 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-13 22:13:57 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-13 22:13:57 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-13 22:13:57 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-13 22:13:57 (9251) [INFO] yum --disablerepo=base ... * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-13 22:13:57 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-13 22:13:57 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] yum-config-manager --disable base * 2025-01-13 22:13:57 (9251) [INFO] or * 2025-01-13 22:13:57 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-13 22:13:57 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-13 22:13:57 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-13 22:13:57 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-13 22:13:57 (9251) [INFO] compromise: * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-13 22:13:57 (9251) [INFO] * 2025-01-13 22:13:57 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-13 22:13: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-13 22:13:58 (9268) [INFO] * 2025-01-13 22:13: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 * 2025-01-13 22:13:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-13 22:13:58 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-13 22:13:58 (9238) [INFO] * 2025-01-13 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 22:13:58 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-13 22:13:58 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-13 22:13:58 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-13 22:13:58 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-13 22:13:58 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-13 22:13:58 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-13 22:13:58 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-13 22:13:58 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-13 22:13:58 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-13 22:13:58 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-13 22:13:58 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-13 22:13:58 (9268) [INFO] * 2025-01-13 22:13:58 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-13 22:13:58 (9238) [INFO] * 2025-01-13 22:13:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-13 22:13:58 (9251) [INFO] Determining fastest mirrors * 2025-01-13 22:14:00 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-13 22:14:00 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-13 22:14:00 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-13 22:14:00 (9251) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-01-13 22:14: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 22:14:00 (9251) [INFO] Trying other mirror. * 2025-01-13 22:14:00 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-13 22:14:00 (9251) [INFO] * 2025-01-13 22:14:00 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-13 22:14:00 (9251) [INFO] * 2025-01-13 22:14:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-13 22:14:00 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-13 22:14:01 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-13 22:14:01 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-13 22:14:01 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-13 22:14:01 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-13 22:14:01 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-13 22:14:01 (9251) [INFO] yum --disablerepo=base ... * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-13 22:14:01 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-13 22:14:01 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] yum-config-manager --disable base * 2025-01-13 22:14:01 (9251) [INFO] or * 2025-01-13 22:14:01 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-13 22:14:01 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-13 22:14:01 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-13 22:14:01 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-13 22:14:01 (9251) [INFO] compromise: * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-13 22:14:01 (9251) [INFO] * 2025-01-13 22:14:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-13 22:14: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 * 2025-01-13 22:14:01 (9268) [INFO] * 2025-01-13 22:14:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open a ticket with cPanel Support, as outlined here: https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/ * 2025-01-13 22:14:01 (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 22:14:01 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-13 22:14:02 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gCIC0dJ69w/ea_profile.json * 2025-01-13 22:14: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/gCIC0dJ69w/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-13 22:14:04 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-01-14 22:13:42 (10291) [INFO] Self-update of script version 59 requested. * 2025-01-14 22:13:43 (10313) [INFO] Script is up to date. * 2025-01-14 22:13:44 (252) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-01-14 22:13:44 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-01-14 22:13:44 (9238) [INFO] * 2025-01-14 22:13:47 (3963) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-01-14 22:13:47 (3970) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-01-14 22:13:47 (9237) [INFO] Running: /usr/bin/yum list extras * 2025-01-14 22:13:47 (9238) [INFO] * 2025-01-14 22:13:52 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-14 22:13:52 (9238) [INFO] * 2025-01-14 22:13:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 22:13:52 (9251) [INFO] Loading mirror speeds from cached hostfile * 2025-01-14 22:13:53 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-14 22:13:53 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-14 22:13:53 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-14 22:13:53 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-14 22:13: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 22:13:53 (9251) [INFO] Trying other mirror. * 2025-01-14 22:13:53 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-14 22:13:53 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-14 22:13:53 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-14 22:13:53 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-14 22:13:53 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-14 22:13:53 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-14 22:13:53 (9251) [INFO] yum --disablerepo=base ... * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-14 22:13:53 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-14 22:13:53 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] yum-config-manager --disable base * 2025-01-14 22:13:53 (9251) [INFO] or * 2025-01-14 22:13:53 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-14 22:13:53 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-14 22:13:53 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-14 22:13:53 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-14 22:13:53 (9251) [INFO] compromise: * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-14 22:13:53 (9251) [INFO] * 2025-01-14 22:13:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-14 22:13: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 22:13:53 (9268) [INFO] * 2025-01-14 22:13: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-14 22:13:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-01-14 22:13:53 (9237) [INFO] Running: /usr/bin/yum clean all * 2025-01-14 22:13:53 (9238) [INFO] * 2025-01-14 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 22:13:54 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-01-14 22:13:54 (9251) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-01-14 22:13:54 (9251) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-01-14 22:13:54 (9251) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-01-14 22:13:54 (9251) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-01-14 22:13:54 (9251) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-01-14 22:13:54 (9251) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-01-14 22:13:54 (9251) [INFO] : mysql-tools-community mysql57-community updates * 2025-01-14 22:13:54 (9251) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-01-14 22:13:54 (9251) [INFO] Cleaning up list of fastest mirrors * 2025-01-14 22:13:54 (9251) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-01-14 22:13:54 (9268) [INFO] * 2025-01-14 22:13:54 (9237) [INFO] Running: /usr/bin/yum makecache * 2025-01-14 22:13:54 (9238) [INFO] * 2025-01-14 22:13:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-01-14 22:13:54 (9251) [INFO] Determining fastest mirrors * 2025-01-14 22:13:56 (9251) [INFO] * EA4: 185.15.22.168 * 2025-01-14 22:13:56 (9251) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-01-14 22:13:56 (9251) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-01-14 22:13:56 (9251) [INFO] * epel: mirrors.hostiserver.com * 2025-01-14 22:13: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-14 22:13:56 (9251) [INFO] Trying other mirror. * 2025-01-14 22:13:56 (9251) [INFO] To address this issue please refer to the below wiki article * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] https://wiki.centos.org/yum-errors * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-01-14 22:13:56 (9251) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-01-14 22:13:56 (9251) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-01-14 22:13:56 (9251) [INFO] upstream. This is most often useful if you are using a newer * 2025-01-14 22:13:56 (9251) [INFO] distribution release than is supported by the repository (and the * 2025-01-14 22:13:56 (9251) [INFO] packages for the previous distribution release still work). * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] 3. Run the command with the repository temporarily disabled * 2025-01-14 22:13:56 (9251) [INFO] yum --disablerepo=base ... * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-01-14 22:13:56 (9251) [INFO] will then just ignore the repository until you permanently enable it * 2025-01-14 22:13:56 (9251) [INFO] again or use --enablerepo for temporary usage: * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] yum-config-manager --disable base * 2025-01-14 22:13:56 (9251) [INFO] or * 2025-01-14 22:13:56 (9251) [INFO] subscription-manager repos --disable=base * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-01-14 22:13:56 (9251) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-01-14 22:13:56 (9251) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-01-14 22:13:56 (9251) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-01-14 22:13:56 (9251) [INFO] compromise: * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-01-14 22:13:56 (9251) [INFO] * 2025-01-14 22:13:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-01-14 22:13: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-14 22:13:56 (9268) [INFO] * 2025-01-14 22:13: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-14 22:13: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-14 22:13:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-01-14 22:13:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yipRoVA_8R/ea_profile.json * 2025-01-14 22:13: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/yipRoVA_8R/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364. * 2025-01-14 22:13:59 (448) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-03-03 22:13:50 (10291) [INFO] Self-update of script version 59 requested. * 2025-03-03 22:13:50 (10296) [INFO] Newer version of script found. Downloading. * 2025-03-03 22:13:51 (10305) [INFO] Script update to version 61 successful. * 2025-03-03 22:13:53 (254) [WARN] *** Elevation Blocker detected: *** disk space issue * 2025-03-03 22:13:53 (254) [WARN] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.53. * 2025-03-03 22:13:53 (9406) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-03-03 22:13:53 (9407) [INFO] * 2025-03-03 22:13:57 (4054) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-03-03 22:13:57 (4061) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-03-03 22:13:57 (9406) [INFO] Running: /usr/bin/yum list extras * 2025-03-03 22:13:57 (9407) [INFO] * 2025-03-03 22:14:02 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-03 22:14:02 (9407) [INFO] * 2025-03-03 22:14:03 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-03 22:14:03 (9420) [INFO] Loading mirror speeds from cached hostfile * 2025-03-03 22:14:04 (9420) [INFO] * EA4: 185.15.22.168 * 2025-03-03 22:14:04 (9420) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-03-03 22:14:04 (9420) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-03-03 22:14:04 (9420) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] One of the configured repositories failed (Unknown), * 2025-03-03 22:14:04 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-03 22:14:04 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-03 22:14:04 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-03 22:14:04 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-03-03 22:14:04 (9420) [INFO] packages for the previous distribution release still work). * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-03 22:14:04 (9420) [INFO] yum --disablerepo= ... * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-03 22:14:04 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-03 22:14:04 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] yum-config-manager --disable * 2025-03-03 22:14:04 (9420) [INFO] or * 2025-03-03 22:14:04 (9420) [INFO] subscription-manager repos --disable= * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-03 22:14:04 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-03 22:14:04 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-03 22:14:04 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-03 22:14:04 (9420) [INFO] compromise: * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-03-03 22:14:04 (9420) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/base * 2025-03-03 22:14:04 (9420) [INFO] * free 0 * 2025-03-03 22:14:04 (9420) [INFO] * needed 100 k * 2025-03-03 22:14:04 (9437) [INFO] * 2025-03-03 22:14:04 (5884) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/base * free 0 * needed 100 k * 2025-03-03 22:14:04 (5885) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-03-03 22:14:04 (9406) [INFO] Running: /usr/bin/yum clean all * 2025-03-03 22:14:04 (9407) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-03 22:14:04 (9420) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-03-03 22:14:04 (9420) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-03-03 22:14:04 (9420) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-03-03 22:14:04 (9420) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-03-03 22:14:04 (9420) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-03-03 22:14:04 (9420) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-03-03 22:14:04 (9420) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-03-03 22:14:04 (9420) [INFO] : mysql-tools-community mysql57-community updates * 2025-03-03 22:14:04 (9420) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-03-03 22:14:04 (9420) [INFO] Cleaning up list of fastest mirrors * 2025-03-03 22:14:04 (9420) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-03-03 22:14:04 (9437) [INFO] * 2025-03-03 22:14:04 (9406) [INFO] Running: /usr/bin/yum makecache * 2025-03-03 22:14:04 (9407) [INFO] * 2025-03-03 22:14:04 (9420) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-03-03 22:14:04 (9420) [INFO] Determining fastest mirrors * 2025-03-03 22:14:06 (9420) [INFO] * EA4: 185.15.22.168 * 2025-03-03 22:14:06 (9420) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-03-03 22:14:06 (9420) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-03-03 22:14:06 (9420) [INFO] * epel: mirrors.hostiserver.com * 2025-03-03 22:14:06 (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-03-03 22:14:06 (9420) [INFO] Trying other mirror. * 2025-03-03 22:14:06 (9420) [INFO] To address this issue please refer to the below wiki article * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] https://wiki.centos.org/yum-errors * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-03-03 22:14:06 (9420) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-03-03 22:14:06 (9420) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-03-03 22:14:06 (9420) [INFO] upstream. This is most often useful if you are using a newer * 2025-03-03 22:14:06 (9420) [INFO] distribution release than is supported by the repository (and the * 2025-03-03 22:14:06 (9420) [INFO] packages for the previous distribution release still work). * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] 3. Run the command with the repository temporarily disabled * 2025-03-03 22:14:06 (9420) [INFO] yum --disablerepo=base ... * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-03-03 22:14:06 (9420) [INFO] will then just ignore the repository until you permanently enable it * 2025-03-03 22:14:06 (9420) [INFO] again or use --enablerepo for temporary usage: * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] yum-config-manager --disable base * 2025-03-03 22:14:06 (9420) [INFO] or * 2025-03-03 22:14:06 (9420) [INFO] subscription-manager repos --disable=base * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-03-03 22:14:06 (9420) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-03-03 22:14:06 (9420) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-03-03 22:14:06 (9420) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-03-03 22:14:06 (9420) [INFO] compromise: * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-03-03 22:14:06 (9420) [INFO] * 2025-03-03 22:14:06 (9420) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-03-03 22:14:06 (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-03-03 22:14:06 (9437) [INFO] * 2025-03-03 22:14:06 (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-03-03 22:14:06 (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-03-03 22:14:06 (2012) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-03-03 22:14:07 (8531) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zTMjh_0i40/ea_profile.json * 2025-03-03 22:14:09 (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/zTMjh_0i40/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8533. * 2025-03-03 22:14:09 (454) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-11 22:13:52 (10464) [INFO] Self-update of script version 61 requested. * 2025-06-11 22:13:52 (10469) [INFO] Newer version of script found. Downloading. * 2025-06-11 22:13:53 (10478) [INFO] Script update to version 66 successful. * 2025-06-11 22:13:55 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-11 22:13:55 (10169) [INFO] * 2025-06-11 22:15:36 (10199) [INFO] * 2025-06-11 22:15:36 (259) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-06-11 22:15:36 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.67. * 2025-06-11 22:15:36 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-11 22:15:36 (10169) [INFO] * 2025-06-11 22:15:41 (4385) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-06-11 22:15:41 (4392) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-11 22:15:41 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-11 22:15:41 (10169) [INFO] * 2025-06-11 22:15:47 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-11 22:15:47 (10169) [INFO] * 2025-06-11 22:15:47 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 22:15:47 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-11 22:15:48 (10182) [INFO] * EA4: 185.90.57.221 * 2025-06-11 22:15:48 (10182) [INFO] * cpanel-addons-production-feed: 185.90.57.221 * 2025-06-11 22:15:48 (10182) [INFO] * cpanel-plugins: 185.90.57.221 * 2025-06-11 22:15:48 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-11 22:15:48 (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 22:15:48 (10182) [INFO] Trying other mirror. * 2025-06-11 22:15:48 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-11 22:15:48 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-11 22:15:48 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-11 22:15:48 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-11 22:15:48 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-11 22:15:48 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-11 22:15:48 (10182) [INFO] yum --disablerepo=base ... * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-11 22:15:48 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-11 22:15:48 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] yum-config-manager --disable base * 2025-06-11 22:15:48 (10182) [INFO] or * 2025-06-11 22:15:48 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-11 22:15:48 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-11 22:15:48 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-11 22:15:48 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-11 22:15:48 (10182) [INFO] compromise: * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-11 22:15:48 (10182) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-11 22:15:48 (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 22:15:48 (10199) [INFO] * 2025-06-11 22:15:48 (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 22:15:48 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-11 22:15:48 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-11 22:15:48 (10169) [INFO] * 2025-06-11 22:15:48 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 22:15:49 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-06-11 22:15:49 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-11 22:15:49 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-11 22:15:49 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-06-11 22:15:49 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-11 22:15:49 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-11 22:15:49 (10182) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-06-11 22:15:49 (10182) [INFO] : mysql-tools-community mysql57-community updates * 2025-06-11 22:15:49 (10182) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-06-11 22:15:49 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-11 22:15:49 (10182) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-06-11 22:15:49 (10199) [INFO] * 2025-06-11 22:15:49 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-11 22:15:49 (10169) [INFO] * 2025-06-11 22:15:49 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-11 22:15:49 (10182) [INFO] Determining fastest mirrors * 2025-06-11 22:15:51 (10182) [INFO] * EA4: 185.15.22.168 * 2025-06-11 22:15:51 (10182) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-06-11 22:15:51 (10182) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-06-11 22:15:51 (10182) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-06-11 22:15:51 (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 22:15:51 (10182) [INFO] Trying other mirror. * 2025-06-11 22:15:51 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-11 22:15:51 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-11 22:15:51 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-11 22:15:51 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-11 22:15:51 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-11 22:15:51 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-11 22:15:51 (10182) [INFO] yum --disablerepo=base ... * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-11 22:15:51 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-11 22:15:51 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] yum-config-manager --disable base * 2025-06-11 22:15:51 (10182) [INFO] or * 2025-06-11 22:15:51 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-11 22:15:51 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-11 22:15:51 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-11 22:15:51 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-11 22:15:51 (10182) [INFO] compromise: * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-11 22:15:51 (10182) [INFO] * 2025-06-11 22:15:51 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-11 22:15:51 (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 22:15:51 (10199) [INFO] * 2025-06-11 22:15:51 (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 22:15:51 (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 22:15:52 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-11 22:15:54 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZeX5Bl6qMu/ea_profile.json * 2025-06-11 22:15:55 (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/ZeX5Bl6qMu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-11 22:15:55 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-12 22:13:32 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-12 22:13:32 (11252) [INFO] Script is up to date. * 2025-06-12 22:13:33 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-12 22:13:33 (10169) [INFO] * 2025-06-12 22:14:14 (10199) [INFO] * 2025-06-12 22:14:14 (259) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-06-12 22:14:14 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Additionally, we were unable to determine the expected version for this build. * 2025-06-12 22:14:14 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-12 22:14:14 (10169) [INFO] * 2025-06-12 22:14:18 (4385) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-06-12 22:14:18 (4392) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-12 22:14:18 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-12 22:14:18 (10169) [INFO] * 2025-06-12 22:14:23 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-12 22:14:23 (10169) [INFO] * 2025-06-12 22:14:23 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 22:14:23 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-12 22:14:24 (10182) [INFO] * EA4: 185.90.57.221 * 2025-06-12 22:14:24 (10182) [INFO] * cpanel-addons-production-feed: 185.90.57.221 * 2025-06-12 22:14:24 (10182) [INFO] * cpanel-plugins: 185.90.57.221 * 2025-06-12 22:14:24 (10182) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-06-12 22:14:24 (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 22:14:24 (10182) [INFO] Trying other mirror. * 2025-06-12 22:14:24 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-12 22:14:24 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-12 22:14:24 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-12 22:14:24 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-12 22:14:24 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-12 22:14:24 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-12 22:14:24 (10182) [INFO] yum --disablerepo=base ... * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-12 22:14:24 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-12 22:14:24 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] yum-config-manager --disable base * 2025-06-12 22:14:24 (10182) [INFO] or * 2025-06-12 22:14:24 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-12 22:14:24 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-12 22:14:24 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-12 22:14:24 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-12 22:14:24 (10182) [INFO] compromise: * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-12 22:14:24 (10182) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-12 22:14:24 (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 22:14:24 (10199) [INFO] * 2025-06-12 22:14:24 (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 22:14:24 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-12 22:14:24 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-12 22:14:24 (10169) [INFO] * 2025-06-12 22:14:24 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 22:14:24 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-06-12 22:14:24 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-12 22:14:24 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-12 22:14:24 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-06-12 22:14:24 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-12 22:14:24 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-12 22:14:24 (10182) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-06-12 22:14:24 (10182) [INFO] : mysql-tools-community mysql57-community updates * 2025-06-12 22:14:24 (10182) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-06-12 22:14:24 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-12 22:14:24 (10182) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-06-12 22:14:24 (10199) [INFO] * 2025-06-12 22:14:24 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-12 22:14:24 (10169) [INFO] * 2025-06-12 22:14:25 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-12 22:14:25 (10182) [INFO] Determining fastest mirrors * 2025-06-12 22:14:26 (10182) [INFO] * EA4: 185.90.57.221 * 2025-06-12 22:14:26 (10182) [INFO] * cpanel-addons-production-feed: 185.90.57.221 * 2025-06-12 22:14:26 (10182) [INFO] * cpanel-plugins: 185.90.57.221 * 2025-06-12 22:14:26 (10182) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-06-12 22:14:26 (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 22:14:26 (10182) [INFO] Trying other mirror. * 2025-06-12 22:14:26 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-12 22:14:26 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-12 22:14:26 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-12 22:14:26 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-12 22:14:26 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-12 22:14:26 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-12 22:14:26 (10182) [INFO] yum --disablerepo=base ... * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-12 22:14:26 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-12 22:14:26 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] yum-config-manager --disable base * 2025-06-12 22:14:26 (10182) [INFO] or * 2025-06-12 22:14:26 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-12 22:14:26 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-12 22:14:26 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-12 22:14:26 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-12 22:14:26 (10182) [INFO] compromise: * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-12 22:14:26 (10182) [INFO] * 2025-06-12 22:14:26 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-12 22:14:26 (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 22:14:26 (10199) [INFO] * 2025-06-12 22:14:26 (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 22:14:26 (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 22:14:27 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-12 22:14:28 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Z1BbjVe3i3/ea_profile.json * 2025-06-12 22:14:29 (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/Z1BbjVe3i3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-12 22:14:29 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-06-13 22:13:37 (11230) [INFO] Self-update of script version 66 requested. * 2025-06-13 22:13:37 (11252) [INFO] Script is up to date. * 2025-06-13 22:13:38 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-06-13 22:13:38 (10169) [INFO] * 2025-06-13 22:14:15 (10199) [INFO] * 2025-06-13 22:14:15 (259) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-06-13 22:14:15 (259) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.68. * 2025-06-13 22:14:15 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-06-13 22:14:15 (10169) [INFO] * 2025-06-13 22:14:18 (4385) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-06-13 22:14:18 (4392) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-06-13 22:14:18 (10168) [INFO] Running: /usr/bin/yum list extras * 2025-06-13 22:14:18 (10169) [INFO] * 2025-06-13 22:14:21 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-13 22:14:21 (10169) [INFO] * 2025-06-13 22:14:21 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 22:14:21 (10182) [INFO] Loading mirror speeds from cached hostfile * 2025-06-13 22:14:22 (10182) [INFO] * EA4: 185.15.22.168 * 2025-06-13 22:14:22 (10182) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-06-13 22:14:22 (10182) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-06-13 22:14:22 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-13 22:14:22 (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 22:14:22 (10182) [INFO] Trying other mirror. * 2025-06-13 22:14:22 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-13 22:14:22 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-13 22:14:22 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-13 22:14:22 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-13 22:14:22 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-13 22:14:22 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-13 22:14:22 (10182) [INFO] yum --disablerepo=base ... * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-13 22:14:22 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-13 22:14:22 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] yum-config-manager --disable base * 2025-06-13 22:14:22 (10182) [INFO] or * 2025-06-13 22:14:22 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-13 22:14:22 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-13 22:14:22 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-13 22:14:22 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-13 22:14:22 (10182) [INFO] compromise: * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-13 22:14:22 (10182) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-13 22:14:22 (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 22:14:22 (10199) [INFO] * 2025-06-13 22:14:22 (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 22:14:22 (6387) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-06-13 22:14:22 (10168) [INFO] Running: /usr/bin/yum clean all * 2025-06-13 22:14:22 (10169) [INFO] * 2025-06-13 22:14:22 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 22:14:22 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-06-13 22:14:22 (10182) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-06-13 22:14:22 (10182) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-06-13 22:14:22 (10182) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-06-13 22:14:22 (10182) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-06-13 22:14:22 (10182) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-06-13 22:14:22 (10182) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-06-13 22:14:22 (10182) [INFO] : mysql-tools-community mysql57-community updates * 2025-06-13 22:14:22 (10182) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-06-13 22:14:23 (10182) [INFO] Cleaning up list of fastest mirrors * 2025-06-13 22:14:23 (10182) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-06-13 22:14:23 (10199) [INFO] * 2025-06-13 22:14:23 (10168) [INFO] Running: /usr/bin/yum makecache * 2025-06-13 22:14:23 (10169) [INFO] * 2025-06-13 22:14:23 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-06-13 22:14:23 (10182) [INFO] Determining fastest mirrors * 2025-06-13 22:14:24 (10182) [INFO] * EA4: 185.15.22.168 * 2025-06-13 22:14:24 (10182) [INFO] * cpanel-addons-production-feed: 185.15.22.168 * 2025-06-13 22:14:24 (10182) [INFO] * cpanel-plugins: 185.15.22.168 * 2025-06-13 22:14:24 (10182) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-06-13 22:14:24 (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 22:14:24 (10182) [INFO] Trying other mirror. * 2025-06-13 22:14:24 (10182) [INFO] To address this issue please refer to the below wiki article * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] https://wiki.centos.org/yum-errors * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/. * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] One of the configured repositories failed (CentOS-7 - Base), * 2025-06-13 22:14:24 (10182) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-06-13 22:14:24 (10182) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-06-13 22:14:24 (10182) [INFO] upstream. This is most often useful if you are using a newer * 2025-06-13 22:14:24 (10182) [INFO] distribution release than is supported by the repository (and the * 2025-06-13 22:14:24 (10182) [INFO] packages for the previous distribution release still work). * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] 3. Run the command with the repository temporarily disabled * 2025-06-13 22:14:24 (10182) [INFO] yum --disablerepo=base ... * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-06-13 22:14:24 (10182) [INFO] will then just ignore the repository until you permanently enable it * 2025-06-13 22:14:24 (10182) [INFO] again or use --enablerepo for temporary usage: * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] yum-config-manager --disable base * 2025-06-13 22:14:24 (10182) [INFO] or * 2025-06-13 22:14:24 (10182) [INFO] subscription-manager repos --disable=base * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-06-13 22:14:24 (10182) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-06-13 22:14:24 (10182) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-06-13 22:14:24 (10182) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-06-13 22:14:24 (10182) [INFO] compromise: * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] yum-config-manager --save --setopt=base.skip_if_unavailable=true * 2025-06-13 22:14:24 (10182) [INFO] * 2025-06-13 22:14:24 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try. * 2025-06-13 22:14:24 (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 22:14:24 (10199) [INFO] * 2025-06-13 22:14:24 (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 22:14:24 (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 22:14:25 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-06-13 22:14:25 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ODkwL97sua/ea_profile.json * 2025-06-13 22:14:27 (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/ODkwL97sua/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290. * 2025-06-13 22:14:27 (476) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-07-31 22:13:56 (11230) [INFO] Self-update of script version 66 requested. * 2025-07-31 22:13:56 (11235) [INFO] Newer version of script found. Downloading. * 2025-07-31 22:13:56 (11244) [INFO] Script update to version 68 successful. * 2025-07-31 22:13:58 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-07-31 22:13:58 (10280) [INFO] * 2025-07-31 22:14:55 (10310) [INFO] * 2025-07-31 22:14:55 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-07-31 22:14:55 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-07-31 22:14:55 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-07-31 22:14:55 (10280) [INFO] * 2025-07-31 22:14:59 (4387) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-07-31 22:14:59 (4394) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-07-31 22:14:59 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-07-31 22:14:59 (10280) [INFO] * 2025-07-31 22:15:03 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-31 22:15:03 (10280) [INFO] * 2025-07-31 22:15:03 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 22:15:03 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-07-31 22:15:04 (10293) [INFO] * EA4: 91.99.144.170 * 2025-07-31 22:15:04 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-07-31 22:15:04 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-07-31 22:15:04 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-31 22:15:04 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-31 22:15:04 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-31 22:15:04 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-31 22:15:04 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-31 22:15:04 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-31 22:15:04 (10293) [INFO] yum --disablerepo= ... * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-31 22:15:04 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-31 22:15:04 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] yum-config-manager --disable * 2025-07-31 22:15:04 (10293) [INFO] or * 2025-07-31 22:15:04 (10293) [INFO] subscription-manager repos --disable= * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-31 22:15:04 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-31 22:15:04 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-31 22:15:04 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-31 22:15:04 (10293) [INFO] compromise: * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-31 22:15:04 (10293) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-07-31 22:15:04 (10293) [INFO] * free 0 * 2025-07-31 22:15:04 (10293) [INFO] * needed 100 k * 2025-07-31 22:15:04 (10310) [INFO] * 2025-07-31 22:15:04 (6388) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-07-31 22:15:04 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-07-31 22:15:04 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-07-31 22:15:04 (10280) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 22:15:04 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-07-31 22:15:04 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-07-31 22:15:04 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-07-31 22:15:04 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-07-31 22:15:04 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-07-31 22:15:04 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-07-31 22:15:04 (10293) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-07-31 22:15:04 (10293) [INFO] : mysql-tools-community mysql57-community updates * 2025-07-31 22:15:04 (10293) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-07-31 22:15:04 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-07-31 22:15:04 (10293) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-07-31 22:15:04 (10310) [INFO] * 2025-07-31 22:15:04 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-07-31 22:15:04 (10280) [INFO] * 2025-07-31 22:15:04 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-07-31 22:15:04 (10293) [INFO] Determining fastest mirrors * 2025-07-31 22:15:07 (10293) [INFO] * EA4: 91.99.144.170 * 2025-07-31 22:15:07 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-07-31 22:15:07 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-07-31 22:15:07 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-07-31 22:15:07 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-07-31 22:15:07 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-07-31 22:15:07 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-07-31 22:15:07 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-07-31 22:15:07 (10293) [INFO] packages for the previous distribution release still work). * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-07-31 22:15:07 (10293) [INFO] yum --disablerepo= ... * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-07-31 22:15:07 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-07-31 22:15:07 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] yum-config-manager --disable * 2025-07-31 22:15:07 (10293) [INFO] or * 2025-07-31 22:15:07 (10293) [INFO] subscription-manager repos --disable= * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-07-31 22:15:07 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-07-31 22:15:07 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-07-31 22:15:07 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-07-31 22:15:07 (10293) [INFO] compromise: * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-07-31 22:15:07 (10293) [INFO] * 2025-07-31 22:15:07 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-07-31 22:15:07 (10293) [INFO] * free 0 * 2025-07-31 22:15:07 (10293) [INFO] * needed 100 k * 2025-07-31 22:15:07 (10310) [INFO] * 2025-07-31 22:15:07 (6398) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-07-31 22:15:07 (6399) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-07-31 22:15:07 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-07-31 22:15:08 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9MIXUxBlfw/ea_profile.json * 2025-07-31 22:15:09 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9MIXUxBlfw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-07-31 22:15:09 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-01 22:13:52 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-01 22:13:52 (11365) [INFO] Script is up to date. * 2025-08-01 22:13:53 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-01 22:13:53 (10280) [INFO] * 2025-08-01 22:15:01 (10310) [INFO] * 2025-08-01 22:15:01 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-01 22:15:01 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-01 22:15:01 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-01 22:15:01 (10280) [INFO] * 2025-08-01 22:15:06 (4387) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-01 22:15:06 (4394) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-01 22:15:06 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-01 22:15:06 (10280) [INFO] * 2025-08-01 22:15:12 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-01 22:15:12 (10280) [INFO] * 2025-08-01 22:15:13 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 22:15:13 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-01 22:15:14 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-01 22:15:14 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-01 22:15:14 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-01 22:15:14 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-01 22:15:14 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-01 22:15:14 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-01 22:15:14 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-01 22:15:14 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-01 22:15:14 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-01 22:15:14 (10293) [INFO] yum --disablerepo= ... * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-01 22:15:14 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-01 22:15:14 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] yum-config-manager --disable * 2025-08-01 22:15:14 (10293) [INFO] or * 2025-08-01 22:15:14 (10293) [INFO] subscription-manager repos --disable= * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-01 22:15:14 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-01 22:15:14 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-01 22:15:14 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-01 22:15:14 (10293) [INFO] compromise: * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-01 22:15:14 (10293) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-01 22:15:14 (10293) [INFO] * free 0 * 2025-08-01 22:15:14 (10293) [INFO] * needed 100 k * 2025-08-01 22:15:14 (10310) [INFO] * 2025-08-01 22:15:14 (6388) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-01 22:15:14 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-01 22:15:14 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-01 22:15:14 (10280) [INFO] * 2025-08-01 22:15:14 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 22:15:14 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-01 22:15:14 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-01 22:15:14 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-01 22:15:14 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-01 22:15:14 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-01 22:15:14 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-01 22:15:14 (10293) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-01 22:15:14 (10293) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-01 22:15:14 (10293) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-01 22:15:14 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-01 22:15:14 (10293) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-01 22:15:14 (10310) [INFO] * 2025-08-01 22:15:14 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-01 22:15:14 (10280) [INFO] * 2025-08-01 22:15:15 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-01 22:15:15 (10293) [INFO] Determining fastest mirrors * 2025-08-01 22:15:18 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-01 22:15:18 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-01 22:15:18 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-01 22:15:18 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-01 22:15:18 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-01 22:15:18 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-01 22:15:18 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-01 22:15:18 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-01 22:15:18 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-01 22:15:18 (10293) [INFO] yum --disablerepo= ... * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-01 22:15:18 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-01 22:15:18 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] yum-config-manager --disable * 2025-08-01 22:15:18 (10293) [INFO] or * 2025-08-01 22:15:18 (10293) [INFO] subscription-manager repos --disable= * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-01 22:15:18 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-01 22:15:18 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-01 22:15:18 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-01 22:15:18 (10293) [INFO] compromise: * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-01 22:15:18 (10293) [INFO] * 2025-08-01 22:15:18 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-01 22:15:18 (10293) [INFO] * free 0 * 2025-08-01 22:15:18 (10293) [INFO] * needed 100 k * 2025-08-01 22:15:18 (10310) [INFO] * 2025-08-01 22:15:18 (6398) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-01 22:15:18 (6399) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-01 22:15:19 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-01 22:15:19 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QjYQZkxh6c/ea_profile.json * 2025-08-01 22:15:20 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QjYQZkxh6c/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-01 22:15:20 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-02 22:14:26 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-02 22:14:27 (11365) [INFO] Script is up to date. * 2025-08-02 22:14:28 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-02 22:14:28 (10280) [INFO] * 2025-08-02 22:15:10 (10310) [INFO] * 2025-08-02 22:15:10 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-02 22:15:10 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-02 22:15:10 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-02 22:15:10 (10280) [INFO] * 2025-08-02 22:15:14 (4387) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-02 22:15:14 (4394) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-02 22:15:14 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-02 22:15:14 (10280) [INFO] * 2025-08-02 22:15:18 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-02 22:15:18 (10280) [INFO] * 2025-08-02 22:15:18 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 22:15:18 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-02 22:15:19 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-02 22:15:19 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-02 22:15:19 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-02 22:15:19 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-02 22:15:19 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-02 22:15:19 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-02 22:15:19 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-02 22:15:19 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-02 22:15:19 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-02 22:15:19 (10293) [INFO] yum --disablerepo= ... * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-02 22:15:19 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-02 22:15:19 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] yum-config-manager --disable * 2025-08-02 22:15:19 (10293) [INFO] or * 2025-08-02 22:15:19 (10293) [INFO] subscription-manager repos --disable= * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-02 22:15:19 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-02 22:15:19 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-02 22:15:19 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-02 22:15:19 (10293) [INFO] compromise: * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-02 22:15:19 (10293) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-02 22:15:19 (10293) [INFO] * free 0 * 2025-08-02 22:15:19 (10293) [INFO] * needed 100 k * 2025-08-02 22:15:19 (10310) [INFO] * 2025-08-02 22:15:19 (6388) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-02 22:15:19 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-02 22:15:19 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-02 22:15:19 (10280) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 22:15:19 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-02 22:15:19 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-02 22:15:19 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-02 22:15:19 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-02 22:15:19 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-02 22:15:19 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-02 22:15:19 (10293) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-02 22:15:19 (10293) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-02 22:15:19 (10293) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-02 22:15:19 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-02 22:15:19 (10293) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-02 22:15:19 (10310) [INFO] * 2025-08-02 22:15:19 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-02 22:15:19 (10280) [INFO] * 2025-08-02 22:15:19 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-02 22:15:20 (10293) [INFO] Determining fastest mirrors * 2025-08-02 22:15:22 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-02 22:15:22 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-02 22:15:22 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-02 22:15:22 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-02 22:15:22 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-02 22:15:22 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-02 22:15:22 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-02 22:15:22 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-02 22:15:22 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-02 22:15:22 (10293) [INFO] yum --disablerepo= ... * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-02 22:15:22 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-02 22:15:22 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] yum-config-manager --disable * 2025-08-02 22:15:22 (10293) [INFO] or * 2025-08-02 22:15:22 (10293) [INFO] subscription-manager repos --disable= * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-02 22:15:22 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-02 22:15:22 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-02 22:15:22 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-02 22:15:22 (10293) [INFO] compromise: * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-02 22:15:22 (10293) [INFO] * 2025-08-02 22:15:22 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-02 22:15:22 (10293) [INFO] * free 0 * 2025-08-02 22:15:22 (10293) [INFO] * needed 100 k * 2025-08-02 22:15:22 (10310) [INFO] * 2025-08-02 22:15:22 (6398) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-02 22:15:22 (6399) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-02 22:15:23 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-02 22:15:24 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pkNDBdcaeJ/ea_profile.json * 2025-08-02 22:15:25 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pkNDBdcaeJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-02 22:15:25 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-03 22:14:26 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-03 22:14:26 (11365) [INFO] Script is up to date. * 2025-08-03 22:14:28 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-03 22:14:28 (10280) [INFO] * 2025-08-03 22:15:11 (10310) [INFO] * 2025-08-03 22:15:11 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-03 22:15:11 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-03 22:15:11 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-03 22:15:11 (10280) [INFO] * 2025-08-03 22:15:15 (4387) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-03 22:15:15 (4394) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-03 22:15:15 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-03 22:15:15 (10280) [INFO] * 2025-08-03 22:15:18 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-03 22:15:18 (10280) [INFO] * 2025-08-03 22:15:18 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 22:15:18 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-03 22:15:19 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-03 22:15:19 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-03 22:15:19 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-03 22:15:19 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-03 22:15:19 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-03 22:15:19 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-03 22:15:19 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-03 22:15:19 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-03 22:15:19 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-03 22:15:19 (10293) [INFO] yum --disablerepo= ... * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-03 22:15:19 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-03 22:15:19 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] yum-config-manager --disable * 2025-08-03 22:15:19 (10293) [INFO] or * 2025-08-03 22:15:19 (10293) [INFO] subscription-manager repos --disable= * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-03 22:15:19 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-03 22:15:19 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-03 22:15:19 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-03 22:15:19 (10293) [INFO] compromise: * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-03 22:15:19 (10293) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/cpanel-plugins * 2025-08-03 22:15:19 (10293) [INFO] * free 0 * 2025-08-03 22:15:19 (10293) [INFO] * needed 100 k * 2025-08-03 22:15:19 (10310) [INFO] * 2025-08-03 22:15:19 (6388) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/cpanel-plugins * free 0 * needed 100 k * 2025-08-03 22:15:19 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-03 22:15:19 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-03 22:15:19 (10280) [INFO] * 2025-08-03 22:15:19 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 22:15:20 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-03 22:15:20 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-03 22:15:20 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-03 22:15:20 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-03 22:15:20 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-03 22:15:20 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-03 22:15:20 (10293) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-03 22:15:20 (10293) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-03 22:15:20 (10293) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-03 22:15:20 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-03 22:15:20 (10293) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-03 22:15:20 (10310) [INFO] * 2025-08-03 22:15:20 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-03 22:15:20 (10280) [INFO] * 2025-08-03 22:15:20 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-03 22:15:20 (10293) [INFO] Determining fastest mirrors * 2025-08-03 22:15:22 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-03 22:15:22 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-03 22:15:22 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-03 22:15:22 (10293) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-03 22:15:22 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-03 22:15:22 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-03 22:15:22 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-03 22:15:22 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-03 22:15:22 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-03 22:15:22 (10293) [INFO] yum --disablerepo= ... * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-03 22:15:22 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-03 22:15:22 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] yum-config-manager --disable * 2025-08-03 22:15:22 (10293) [INFO] or * 2025-08-03 22:15:22 (10293) [INFO] subscription-manager repos --disable= * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-03 22:15:22 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-03 22:15:22 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-03 22:15:22 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-03 22:15:22 (10293) [INFO] compromise: * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-03 22:15:22 (10293) [INFO] * 2025-08-03 22:15:22 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-03 22:15:22 (10293) [INFO] * free 0 * 2025-08-03 22:15:22 (10293) [INFO] * needed 100 k * 2025-08-03 22:15:22 (10310) [INFO] * 2025-08-03 22:15:22 (6398) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-03 22:15:22 (6399) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-03 22:15:23 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-03 22:15:23 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xNO2U_buPt/ea_profile.json * 2025-08-03 22:15:24 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xNO2U_buPt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-03 22:15:24 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-04 22:13:37 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-04 22:13:38 (11365) [INFO] Script is up to date. * 2025-08-04 22:13:39 (10279) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-04 22:13:39 (10280) [INFO] * 2025-08-04 22:14:30 (10310) [INFO] * 2025-08-04 22:14:30 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-04 22:14:30 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-04 22:14:30 (10279) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-04 22:14:30 (10280) [INFO] * 2025-08-04 22:14:33 (4387) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-04 22:14:33 (4394) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-04 22:14:33 (10279) [INFO] Running: /usr/bin/yum list extras * 2025-08-04 22:14:33 (10280) [INFO] * 2025-08-04 22:14:37 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-04 22:14:37 (10280) [INFO] * 2025-08-04 22:14:37 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 22:14:37 (10293) [INFO] Loading mirror speeds from cached hostfile * 2025-08-04 22:14:38 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-04 22:14:38 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-04 22:14:38 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-04 22:14:38 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-04 22:14:38 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-04 22:14:38 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-04 22:14:38 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-04 22:14:38 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-04 22:14:38 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-04 22:14:38 (10293) [INFO] yum --disablerepo= ... * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-04 22:14:38 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-04 22:14:38 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] yum-config-manager --disable * 2025-08-04 22:14:38 (10293) [INFO] or * 2025-08-04 22:14:38 (10293) [INFO] subscription-manager repos --disable= * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-04 22:14:38 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-04 22:14:38 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-04 22:14:38 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-04 22:14:38 (10293) [INFO] compromise: * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-04 22:14:38 (10293) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-04 22:14:38 (10293) [INFO] * free 0 * 2025-08-04 22:14:38 (10293) [INFO] * needed 100 k * 2025-08-04 22:14:38 (10310) [INFO] * 2025-08-04 22:14:38 (6388) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-04 22:14:38 (6389) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-04 22:14:38 (10279) [INFO] Running: /usr/bin/yum clean all * 2025-08-04 22:14:38 (10280) [INFO] * 2025-08-04 22:14:38 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 22:14:39 (10293) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-04 22:14:39 (10293) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-04 22:14:39 (10293) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-04 22:14:39 (10293) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-04 22:14:39 (10293) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-04 22:14:39 (10293) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-04 22:14:39 (10293) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-04 22:14:39 (10293) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-04 22:14:39 (10293) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-04 22:14:39 (10293) [INFO] Cleaning up list of fastest mirrors * 2025-08-04 22:14:39 (10293) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-04 22:14:39 (10310) [INFO] * 2025-08-04 22:14:39 (10279) [INFO] Running: /usr/bin/yum makecache * 2025-08-04 22:14:39 (10280) [INFO] * 2025-08-04 22:14:39 (10293) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-04 22:14:39 (10293) [INFO] Determining fastest mirrors * 2025-08-04 22:14:42 (10293) [INFO] * EA4: 91.99.144.170 * 2025-08-04 22:14:42 (10293) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-04 22:14:42 (10293) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-04 22:14:42 (10293) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] One of the configured repositories failed (Unknown), * 2025-08-04 22:14:42 (10293) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-04 22:14:42 (10293) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-04 22:14:42 (10293) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-04 22:14:42 (10293) [INFO] distribution release than is supported by the repository (and the * 2025-08-04 22:14:42 (10293) [INFO] packages for the previous distribution release still work). * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-04 22:14:42 (10293) [INFO] yum --disablerepo= ... * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-04 22:14:42 (10293) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-04 22:14:42 (10293) [INFO] again or use --enablerepo for temporary usage: * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] yum-config-manager --disable * 2025-08-04 22:14:42 (10293) [INFO] or * 2025-08-04 22:14:42 (10293) [INFO] subscription-manager repos --disable= * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-04 22:14:42 (10293) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-04 22:14:42 (10293) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-04 22:14:42 (10293) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-04 22:14:42 (10293) [INFO] compromise: * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-04 22:14:42 (10293) [INFO] * 2025-08-04 22:14:42 (10293) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-04 22:14:42 (10293) [INFO] * free 0 * 2025-08-04 22:14:42 (10293) [INFO] * needed 100 k * 2025-08-04 22:14:42 (10310) [INFO] * 2025-08-04 22:14:42 (6398) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-04 22:14:42 (6399) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-04 22:14:43 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-04 22:14:44 (9399) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kGTBuk56NG/ea_profile.json * 2025-08-04 22:14:44 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kGTBuk56NG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9401. * 2025-08-04 22:14:44 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-08 22:13:38 (11343) [INFO] Self-update of script version 68 requested. * 2025-08-08 22:13:38 (11348) [INFO] Newer version of script found. Downloading. * 2025-08-08 22:13:39 (11357) [INFO] Script update to version 69 successful. * 2025-08-08 22:13:40 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-08 22:13:40 (10285) [INFO] * 2025-08-08 22:14:20 (10315) [INFO] * 2025-08-08 22:14:20 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-08 22:14:20 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-08 22:14:20 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-08 22:14:20 (10285) [INFO] * 2025-08-08 22:14:24 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-08 22:14:24 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-08 22:14:24 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-08 22:14:24 (10285) [INFO] * 2025-08-08 22:14:26 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-08 22:14:26 (10285) [INFO] * 2025-08-08 22:14:26 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 22:14:26 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-08 22:14:27 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-08 22:14:27 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-08 22:14:27 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-08 22:14:27 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-08 22:14:27 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-08 22:14:27 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-08 22:14:27 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-08 22:14:27 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-08 22:14:27 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-08 22:14:27 (10298) [INFO] yum --disablerepo= ... * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-08 22:14:27 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-08 22:14:27 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] yum-config-manager --disable * 2025-08-08 22:14:27 (10298) [INFO] or * 2025-08-08 22:14:27 (10298) [INFO] subscription-manager repos --disable= * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-08 22:14:27 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-08 22:14:27 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-08 22:14:27 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-08 22:14:27 (10298) [INFO] compromise: * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-08 22:14:27 (10298) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-08 22:14:27 (10298) [INFO] * free 0 * 2025-08-08 22:14:27 (10298) [INFO] * needed 100 k * 2025-08-08 22:14:27 (10315) [INFO] * 2025-08-08 22:14:27 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-08 22:14:27 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-08 22:14:27 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-08 22:14:27 (10285) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 22:14:27 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-08 22:14:27 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-08 22:14:27 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-08 22:14:27 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-08 22:14:27 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-08 22:14:27 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-08 22:14:27 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-08 22:14:27 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-08 22:14:27 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-08 22:14:27 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-08 22:14:27 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-08 22:14:27 (10315) [INFO] * 2025-08-08 22:14:27 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-08 22:14:27 (10285) [INFO] * 2025-08-08 22:14:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-08 22:14:28 (10298) [INFO] Determining fastest mirrors * 2025-08-08 22:14:28 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-08 22:14:28 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-08 22:14:28 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-08 22:14:28 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-08 22:14:28 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-08 22:14:28 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-08 22:14:28 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-08 22:14:28 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-08 22:14:28 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-08 22:14:28 (10298) [INFO] yum --disablerepo= ... * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-08 22:14:28 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-08 22:14:28 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] yum-config-manager --disable * 2025-08-08 22:14:28 (10298) [INFO] or * 2025-08-08 22:14:28 (10298) [INFO] subscription-manager repos --disable= * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-08 22:14:28 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-08 22:14:28 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-08 22:14:28 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-08 22:14:28 (10298) [INFO] compromise: * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-08 22:14:28 (10298) [INFO] * 2025-08-08 22:14:28 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-08 22:14:28 (10298) [INFO] * free 0 * 2025-08-08 22:14:28 (10298) [INFO] * needed 100 k * 2025-08-08 22:14:28 (10315) [INFO] * 2025-08-08 22:14:28 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-08 22:14:28 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-08 22:14:29 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-08 22:14:30 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Mv5TKvNdQP/ea_profile.json * 2025-08-08 22:14:30 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Mv5TKvNdQP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-08 22:14:30 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-09 22:14:18 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-09 22:14:18 (11370) [INFO] Script is up to date. * 2025-08-09 22:14:19 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-09 22:14:19 (10285) [INFO] * 2025-08-09 22:14:53 (10315) [INFO] * 2025-08-09 22:14:53 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-09 22:14:53 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-09 22:14:53 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-09 22:14:53 (10285) [INFO] * 2025-08-09 22:14:56 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-09 22:14:56 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-09 22:14:56 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-09 22:14:56 (10285) [INFO] * 2025-08-09 22:14:59 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-09 22:14:59 (10285) [INFO] * 2025-08-09 22:14:59 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 22:14:59 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-09 22:15:00 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-09 22:15:00 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-09 22:15:00 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-09 22:15:00 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-09 22:15:00 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-09 22:15:00 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-09 22:15:00 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-09 22:15:00 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-09 22:15:00 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-09 22:15:00 (10298) [INFO] yum --disablerepo= ... * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-09 22:15:00 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-09 22:15:00 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] yum-config-manager --disable * 2025-08-09 22:15:00 (10298) [INFO] or * 2025-08-09 22:15:00 (10298) [INFO] subscription-manager repos --disable= * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-09 22:15:00 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-09 22:15:00 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-09 22:15:00 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-09 22:15:00 (10298) [INFO] compromise: * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-09 22:15:00 (10298) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-09 22:15:00 (10298) [INFO] * free 0 * 2025-08-09 22:15:00 (10298) [INFO] * needed 100 k * 2025-08-09 22:15:00 (10315) [INFO] * 2025-08-09 22:15:00 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-09 22:15:00 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-09 22:15:00 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-09 22:15:00 (10285) [INFO] * 2025-08-09 22:15:00 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 22:15:01 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-09 22:15:01 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-09 22:15:01 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-09 22:15:01 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-09 22:15:01 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-09 22:15:01 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-09 22:15:01 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-09 22:15:01 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-09 22:15:01 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-09 22:15:01 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-09 22:15:01 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-09 22:15:01 (10315) [INFO] * 2025-08-09 22:15:01 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-09 22:15:01 (10285) [INFO] * 2025-08-09 22:15:01 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-09 22:15:01 (10298) [INFO] Determining fastest mirrors * 2025-08-09 22:15:04 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-09 22:15:04 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-09 22:15:04 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-09 22:15:04 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-09 22:15:04 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-09 22:15:04 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-09 22:15:04 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-09 22:15:04 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-09 22:15:04 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-09 22:15:04 (10298) [INFO] yum --disablerepo= ... * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-09 22:15:04 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-09 22:15:04 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] yum-config-manager --disable * 2025-08-09 22:15:04 (10298) [INFO] or * 2025-08-09 22:15:04 (10298) [INFO] subscription-manager repos --disable= * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-09 22:15:04 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-09 22:15:04 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-09 22:15:04 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-09 22:15:04 (10298) [INFO] compromise: * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-09 22:15:04 (10298) [INFO] * 2025-08-09 22:15:04 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-09 22:15:04 (10298) [INFO] * free 0 * 2025-08-09 22:15:04 (10298) [INFO] * needed 100 k * 2025-08-09 22:15:04 (10315) [INFO] * 2025-08-09 22:15:04 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-09 22:15:04 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-09 22:15:04 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-09 22:15:05 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EJnghuOy8P/ea_profile.json * 2025-08-09 22:15:06 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EJnghuOy8P/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-09 22:15:06 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-10 22:14:14 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-10 22:14:14 (11370) [INFO] Script is up to date. * 2025-08-10 22:14:15 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-10 22:14:15 (10285) [INFO] * 2025-08-10 22:14:50 (10315) [INFO] * 2025-08-10 22:14:50 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-10 22:14:50 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-10 22:14:50 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-10 22:14:50 (10285) [INFO] * 2025-08-10 22:14:53 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-10 22:14:53 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-10 22:14:53 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-10 22:14:53 (10285) [INFO] * 2025-08-10 22:14:56 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-10 22:14:56 (10285) [INFO] * 2025-08-10 22:14:56 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 22:14:56 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-10 22:14:58 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-10 22:14:58 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-10 22:14:58 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-10 22:14:58 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-10 22:14:58 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-10 22:14:58 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-10 22:14:58 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-10 22:14:58 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-10 22:14:58 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-10 22:14:58 (10298) [INFO] yum --disablerepo= ... * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-10 22:14:58 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-10 22:14:58 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] yum-config-manager --disable * 2025-08-10 22:14:58 (10298) [INFO] or * 2025-08-10 22:14:58 (10298) [INFO] subscription-manager repos --disable= * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-10 22:14:58 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-10 22:14:58 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-10 22:14:58 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-10 22:14:58 (10298) [INFO] compromise: * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-10 22:14:58 (10298) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-10 22:14:58 (10298) [INFO] * free 0 * 2025-08-10 22:14:58 (10298) [INFO] * needed 100 k * 2025-08-10 22:14:58 (10315) [INFO] * 2025-08-10 22:14:58 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-10 22:14:58 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-10 22:14:58 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-10 22:14:58 (10285) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 22:14:58 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-10 22:14:58 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-10 22:14:58 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-10 22:14:58 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-10 22:14:58 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-10 22:14:58 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-10 22:14:58 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-10 22:14:58 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-10 22:14:58 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-10 22:14:58 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-10 22:14:58 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-10 22:14:58 (10315) [INFO] * 2025-08-10 22:14:58 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-10 22:14:58 (10285) [INFO] * 2025-08-10 22:14:58 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-10 22:14:59 (10298) [INFO] Determining fastest mirrors * 2025-08-10 22:15:01 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-10 22:15:01 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-10 22:15:01 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-10 22:15:01 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-10 22:15:01 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-10 22:15:01 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-10 22:15:01 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-10 22:15:01 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-10 22:15:01 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-10 22:15:01 (10298) [INFO] yum --disablerepo= ... * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-10 22:15:01 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-10 22:15:01 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] yum-config-manager --disable * 2025-08-10 22:15:01 (10298) [INFO] or * 2025-08-10 22:15:01 (10298) [INFO] subscription-manager repos --disable= * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-10 22:15:01 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-10 22:15:01 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-10 22:15:01 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-10 22:15:01 (10298) [INFO] compromise: * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-10 22:15:01 (10298) [INFO] * 2025-08-10 22:15:01 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-10 22:15:01 (10298) [INFO] * free 0 * 2025-08-10 22:15:01 (10298) [INFO] * needed 100 k * 2025-08-10 22:15:01 (10315) [INFO] * 2025-08-10 22:15:01 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-10 22:15:01 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-10 22:15:02 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-10 22:15:02 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1a1eLbBZYT/ea_profile.json * 2025-08-10 22:15:03 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1a1eLbBZYT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-10 22:15:03 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-11 22:13:38 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-11 22:13:38 (11370) [INFO] Script is up to date. * 2025-08-11 22:13:39 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-11 22:13:39 (10285) [INFO] * 2025-08-11 22:14:19 (10315) [INFO] * 2025-08-11 22:14:19 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-11 22:14:19 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-11 22:14:19 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-11 22:14:19 (10285) [INFO] * 2025-08-11 22:14:22 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-11 22:14:22 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-11 22:14:22 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-11 22:14:22 (10285) [INFO] * 2025-08-11 22:14:25 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-11 22:14:25 (10285) [INFO] * 2025-08-11 22:14:25 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 22:14:25 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-11 22:14:26 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-11 22:14:26 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-11 22:14:26 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-11 22:14:26 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-11 22:14:26 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-11 22:14:26 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-11 22:14:26 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-11 22:14:26 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-11 22:14:26 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-11 22:14:26 (10298) [INFO] yum --disablerepo= ... * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-11 22:14:26 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-11 22:14:26 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] yum-config-manager --disable * 2025-08-11 22:14:26 (10298) [INFO] or * 2025-08-11 22:14:26 (10298) [INFO] subscription-manager repos --disable= * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-11 22:14:26 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-11 22:14:26 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-11 22:14:26 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-11 22:14:26 (10298) [INFO] compromise: * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-11 22:14:26 (10298) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-11 22:14:26 (10298) [INFO] * free 0 * 2025-08-11 22:14:26 (10298) [INFO] * needed 100 k * 2025-08-11 22:14:26 (10315) [INFO] * 2025-08-11 22:14:26 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-11 22:14:26 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-11 22:14:26 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-11 22:14:26 (10285) [INFO] * 2025-08-11 22:14:26 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 22:14:26 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-11 22:14:26 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-11 22:14:26 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-11 22:14:26 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-11 22:14:26 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-11 22:14:26 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-11 22:14:26 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-11 22:14:26 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-11 22:14:26 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-11 22:14:26 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-11 22:14:26 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-11 22:14:26 (10315) [INFO] * 2025-08-11 22:14:26 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-11 22:14:26 (10285) [INFO] * 2025-08-11 22:14:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-11 22:14:27 (10298) [INFO] Determining fastest mirrors * 2025-08-11 22:14:28 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-11 22:14:28 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-11 22:14:28 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-11 22:14:28 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-11 22:14:28 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-11 22:14:28 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-11 22:14:28 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-11 22:14:28 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-11 22:14:28 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-11 22:14:28 (10298) [INFO] yum --disablerepo= ... * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-11 22:14:28 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-11 22:14:28 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] yum-config-manager --disable * 2025-08-11 22:14:28 (10298) [INFO] or * 2025-08-11 22:14:28 (10298) [INFO] subscription-manager repos --disable= * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-11 22:14:28 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-11 22:14:28 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-11 22:14:28 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-11 22:14:28 (10298) [INFO] compromise: * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-11 22:14:28 (10298) [INFO] * 2025-08-11 22:14:28 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-11 22:14:28 (10298) [INFO] * free 0 * 2025-08-11 22:14:28 (10298) [INFO] * needed 100 k * 2025-08-11 22:14:28 (10315) [INFO] * 2025-08-11 22:14:28 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-11 22:14:28 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-11 22:14:28 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-11 22:14:29 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JJiHaMc0zT/ea_profile.json * 2025-08-11 22:14:30 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JJiHaMc0zT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-11 22:14:30 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-12 22:13:41 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-12 22:13:41 (11370) [INFO] Script is up to date. * 2025-08-12 22:13:42 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-12 22:13:42 (10285) [INFO] * 2025-08-12 22:14:19 (10315) [INFO] * 2025-08-12 22:14:19 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-12 22:14:19 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-12 22:14:19 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-12 22:14:19 (10285) [INFO] * 2025-08-12 22:14:22 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-12 22:14:22 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-12 22:14:22 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-12 22:14:22 (10285) [INFO] * 2025-08-12 22:14:24 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-12 22:14:24 (10285) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 22:14:25 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-12 22:14:25 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-12 22:14:25 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-12 22:14:25 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-12 22:14:25 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-12 22:14:25 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-12 22:14:25 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-12 22:14:25 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-12 22:14:25 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-12 22:14:25 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-12 22:14:25 (10298) [INFO] yum --disablerepo= ... * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-12 22:14:25 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-12 22:14:25 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] yum-config-manager --disable * 2025-08-12 22:14:25 (10298) [INFO] or * 2025-08-12 22:14:25 (10298) [INFO] subscription-manager repos --disable= * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-12 22:14:25 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-12 22:14:25 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-12 22:14:25 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-12 22:14:25 (10298) [INFO] compromise: * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-12 22:14:25 (10298) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-12 22:14:25 (10298) [INFO] * free 0 * 2025-08-12 22:14:25 (10298) [INFO] * needed 100 k * 2025-08-12 22:14:25 (10315) [INFO] * 2025-08-12 22:14:25 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-12 22:14:25 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-12 22:14:25 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-12 22:14:25 (10285) [INFO] * 2025-08-12 22:14:25 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 22:14:26 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-12 22:14:26 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-12 22:14:26 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-12 22:14:26 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-12 22:14:26 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-12 22:14:26 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-12 22:14:26 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-12 22:14:26 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-12 22:14:26 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-12 22:14:26 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-12 22:14:26 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-12 22:14:26 (10315) [INFO] * 2025-08-12 22:14:26 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-12 22:14:26 (10285) [INFO] * 2025-08-12 22:14:26 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-12 22:14:26 (10298) [INFO] Determining fastest mirrors * 2025-08-12 22:14:27 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-12 22:14:27 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-12 22:14:27 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-12 22:14:27 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-12 22:14:27 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-12 22:14:27 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-12 22:14:27 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-12 22:14:27 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-12 22:14:27 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-12 22:14:27 (10298) [INFO] yum --disablerepo= ... * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-12 22:14:27 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-12 22:14:27 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] yum-config-manager --disable * 2025-08-12 22:14:27 (10298) [INFO] or * 2025-08-12 22:14:27 (10298) [INFO] subscription-manager repos --disable= * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-12 22:14:27 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-12 22:14:27 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-12 22:14:27 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-12 22:14:27 (10298) [INFO] compromise: * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-12 22:14:27 (10298) [INFO] * 2025-08-12 22:14:27 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-12 22:14:27 (10298) [INFO] * free 0 * 2025-08-12 22:14:27 (10298) [INFO] * needed 100 k * 2025-08-12 22:14:27 (10315) [INFO] * 2025-08-12 22:14:27 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-12 22:14:27 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-12 22:14:27 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-12 22:14:28 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FDFjgE6FT1/ea_profile.json * 2025-08-12 22:14:29 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FDFjgE6FT1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-12 22:14:29 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-13 22:13:37 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-13 22:13:38 (11370) [INFO] Script is up to date. * 2025-08-13 22:13:39 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-13 22:13:39 (10285) [INFO] * 2025-08-13 22:14:20 (10315) [INFO] * 2025-08-13 22:14:20 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-13 22:14:20 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-13 22:14:20 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-13 22:14:20 (10285) [INFO] * 2025-08-13 22:14:23 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-13 22:14:23 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-13 22:14:23 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-13 22:14:23 (10285) [INFO] * 2025-08-13 22:14:26 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-13 22:14:26 (10285) [INFO] * 2025-08-13 22:14:26 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 22:14:26 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-13 22:14:27 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-13 22:14:27 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-13 22:14:27 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-13 22:14:27 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-13 22:14:27 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-13 22:14:27 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-13 22:14:27 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-13 22:14:27 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-13 22:14:27 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-13 22:14:27 (10298) [INFO] yum --disablerepo= ... * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-13 22:14:27 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-13 22:14:27 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] yum-config-manager --disable * 2025-08-13 22:14:27 (10298) [INFO] or * 2025-08-13 22:14:27 (10298) [INFO] subscription-manager repos --disable= * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-13 22:14:27 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-13 22:14:27 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-13 22:14:27 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-13 22:14:27 (10298) [INFO] compromise: * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-13 22:14:27 (10298) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-13 22:14:27 (10298) [INFO] * free 0 * 2025-08-13 22:14:27 (10298) [INFO] * needed 100 k * 2025-08-13 22:14:27 (10315) [INFO] * 2025-08-13 22:14:27 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-13 22:14:27 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-13 22:14:27 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-13 22:14:27 (10285) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 22:14:27 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-13 22:14:27 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-13 22:14:27 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-13 22:14:27 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-13 22:14:27 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-13 22:14:27 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-13 22:14:27 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-13 22:14:27 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-13 22:14:27 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-13 22:14:27 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-13 22:14:27 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-13 22:14:27 (10315) [INFO] * 2025-08-13 22:14:27 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-13 22:14:27 (10285) [INFO] * 2025-08-13 22:14:27 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-13 22:14:28 (10298) [INFO] Determining fastest mirrors * 2025-08-13 22:14:29 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-13 22:14:29 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-13 22:14:29 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-13 22:14:29 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-13 22:14:29 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-13 22:14:29 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-13 22:14:29 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-13 22:14:29 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-13 22:14:29 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-13 22:14:29 (10298) [INFO] yum --disablerepo= ... * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-13 22:14:29 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-13 22:14:29 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] yum-config-manager --disable * 2025-08-13 22:14:29 (10298) [INFO] or * 2025-08-13 22:14:29 (10298) [INFO] subscription-manager repos --disable= * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-13 22:14:29 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-13 22:14:29 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-13 22:14:29 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-13 22:14:29 (10298) [INFO] compromise: * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-13 22:14:29 (10298) [INFO] * 2025-08-13 22:14:29 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-13 22:14:29 (10298) [INFO] * free 0 * 2025-08-13 22:14:29 (10298) [INFO] * needed 100 k * 2025-08-13 22:14:29 (10315) [INFO] * 2025-08-13 22:14:29 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-13 22:14:29 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-13 22:14:29 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-13 22:14:30 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jdou4fS3RW/ea_profile.json * 2025-08-13 22:14:30 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jdou4fS3RW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-13 22:14:30 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-14 22:13:34 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-14 22:13:34 (11370) [INFO] Script is up to date. * 2025-08-14 22:13:35 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-14 22:13:35 (10285) [INFO] * 2025-08-14 22:14:13 (10315) [INFO] * 2025-08-14 22:14:13 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-14 22:14:13 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-14 22:14:13 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-14 22:14:13 (10285) [INFO] * 2025-08-14 22:14:16 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-14 22:14:16 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-14 22:14:16 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-14 22:14:16 (10285) [INFO] * 2025-08-14 22:14:19 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-14 22:14:19 (10285) [INFO] * 2025-08-14 22:14:19 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 22:14:19 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-14 22:14:20 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-14 22:14:20 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-14 22:14:20 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-14 22:14:20 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-14 22:14:20 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-14 22:14:20 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-14 22:14:20 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-14 22:14:20 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-14 22:14:20 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-14 22:14:20 (10298) [INFO] yum --disablerepo= ... * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-14 22:14:20 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-14 22:14:20 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] yum-config-manager --disable * 2025-08-14 22:14:20 (10298) [INFO] or * 2025-08-14 22:14:20 (10298) [INFO] subscription-manager repos --disable= * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-14 22:14:20 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-14 22:14:20 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-14 22:14:20 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-14 22:14:20 (10298) [INFO] compromise: * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-14 22:14:20 (10298) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-14 22:14:20 (10298) [INFO] * free 0 * 2025-08-14 22:14:20 (10298) [INFO] * needed 100 k * 2025-08-14 22:14:20 (10315) [INFO] * 2025-08-14 22:14:20 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-14 22:14:20 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-14 22:14:20 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-14 22:14:20 (10285) [INFO] * 2025-08-14 22:14:20 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 22:14:20 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-14 22:14:20 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-14 22:14:20 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-14 22:14:20 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-14 22:14:20 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-14 22:14:20 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-14 22:14:20 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-14 22:14:20 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-14 22:14:20 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-14 22:14:21 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-14 22:14:21 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-14 22:14:21 (10315) [INFO] * 2025-08-14 22:14:21 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-14 22:14:21 (10285) [INFO] * 2025-08-14 22:14:21 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-14 22:14:21 (10298) [INFO] Determining fastest mirrors * 2025-08-14 22:14:22 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-14 22:14:22 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-14 22:14:22 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-14 22:14:22 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-14 22:14:22 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-14 22:14:22 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-14 22:14:22 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-14 22:14:22 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-14 22:14:22 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-14 22:14:22 (10298) [INFO] yum --disablerepo= ... * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-14 22:14:22 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-14 22:14:22 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] yum-config-manager --disable * 2025-08-14 22:14:22 (10298) [INFO] or * 2025-08-14 22:14:22 (10298) [INFO] subscription-manager repos --disable= * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-14 22:14:22 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-14 22:14:22 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-14 22:14:22 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-14 22:14:22 (10298) [INFO] compromise: * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-14 22:14:22 (10298) [INFO] * 2025-08-14 22:14:22 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-14 22:14:22 (10298) [INFO] * free 0 * 2025-08-14 22:14:22 (10298) [INFO] * needed 100 k * 2025-08-14 22:14:22 (10315) [INFO] * 2025-08-14 22:14:22 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-14 22:14:22 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-14 22:14:23 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-14 22:14:24 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MWcRQkAiFb/ea_profile.json * 2025-08-14 22:14:24 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MWcRQkAiFb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-14 22:14:24 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-16 22:14:22 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-16 22:14:22 (11370) [INFO] Script is up to date. * 2025-08-16 22:14:23 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-16 22:14:23 (10285) [INFO] * 2025-08-16 22:15:01 (10315) [INFO] * 2025-08-16 22:15:01 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-16 22:15:01 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-16 22:15:01 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-16 22:15:01 (10285) [INFO] * 2025-08-16 22:15:05 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-16 22:15:05 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-16 22:15:05 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-16 22:15:05 (10285) [INFO] * 2025-08-16 22:15:08 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-16 22:15:08 (10285) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 22:15:09 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-16 22:15:09 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-16 22:15:09 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-16 22:15:09 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-16 22:15:09 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-16 22:15:09 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-16 22:15:09 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-16 22:15:09 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-16 22:15:09 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-16 22:15:09 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-16 22:15:09 (10298) [INFO] yum --disablerepo= ... * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-16 22:15:09 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-16 22:15:09 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] yum-config-manager --disable * 2025-08-16 22:15:09 (10298) [INFO] or * 2025-08-16 22:15:09 (10298) [INFO] subscription-manager repos --disable= * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-16 22:15:09 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-16 22:15:09 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-16 22:15:09 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-16 22:15:09 (10298) [INFO] compromise: * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-16 22:15:09 (10298) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-16 22:15:09 (10298) [INFO] * free 0 * 2025-08-16 22:15:09 (10298) [INFO] * needed 100 k * 2025-08-16 22:15:09 (10315) [INFO] * 2025-08-16 22:15:09 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-16 22:15:09 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-16 22:15:09 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-16 22:15:09 (10285) [INFO] * 2025-08-16 22:15:09 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 22:15:10 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-16 22:15:10 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-16 22:15:10 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-16 22:15:10 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-16 22:15:10 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-16 22:15:10 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-16 22:15:10 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-16 22:15:10 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-16 22:15:10 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-16 22:15:10 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-16 22:15:10 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-16 22:15:10 (10315) [INFO] * 2025-08-16 22:15:10 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-16 22:15:10 (10285) [INFO] * 2025-08-16 22:15:10 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-16 22:15:10 (10298) [INFO] Determining fastest mirrors * 2025-08-16 22:15:13 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-16 22:15:13 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-16 22:15:13 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-16 22:15:13 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-16 22:15:13 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-16 22:15:13 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-16 22:15:13 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-16 22:15:13 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-16 22:15:13 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-16 22:15:13 (10298) [INFO] yum --disablerepo= ... * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-16 22:15:13 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-16 22:15:13 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] yum-config-manager --disable * 2025-08-16 22:15:13 (10298) [INFO] or * 2025-08-16 22:15:13 (10298) [INFO] subscription-manager repos --disable= * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-16 22:15:13 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-16 22:15:13 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-16 22:15:13 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-16 22:15:13 (10298) [INFO] compromise: * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-16 22:15:13 (10298) [INFO] * 2025-08-16 22:15:13 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-16 22:15:13 (10298) [INFO] * free 0 * 2025-08-16 22:15:13 (10298) [INFO] * needed 100 k * 2025-08-16 22:15:13 (10315) [INFO] * 2025-08-16 22:15:13 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-16 22:15:13 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-16 22:15:13 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-16 22:15:14 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bvN89EhFGI/ea_profile.json * 2025-08-16 22:15:15 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bvN89EhFGI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-16 22:15:15 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-17 22:14:27 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-17 22:14:27 (11370) [INFO] Script is up to date. * 2025-08-17 22:14:28 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-17 22:14:28 (10285) [INFO] * 2025-08-17 22:15:10 (10315) [INFO] * 2025-08-17 22:15:10 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-17 22:15:11 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-17 22:15:11 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-17 22:15:11 (10285) [INFO] * 2025-08-17 22:15:16 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-17 22:15:16 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-17 22:15:16 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-17 22:15:16 (10285) [INFO] * 2025-08-17 22:15:21 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-17 22:15:21 (10285) [INFO] * 2025-08-17 22:15:21 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 22:15:21 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-17 22:15:22 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-17 22:15:22 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-17 22:15:22 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-17 22:15:22 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-17 22:15:22 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-17 22:15:22 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-17 22:15:22 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-17 22:15:22 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-17 22:15:22 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-17 22:15:22 (10298) [INFO] yum --disablerepo= ... * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-17 22:15:22 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-17 22:15:22 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] yum-config-manager --disable * 2025-08-17 22:15:22 (10298) [INFO] or * 2025-08-17 22:15:22 (10298) [INFO] subscription-manager repos --disable= * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-17 22:15:22 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-17 22:15:22 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-17 22:15:22 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-17 22:15:22 (10298) [INFO] compromise: * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-17 22:15:22 (10298) [INFO] * 2025-08-17 22:15:22 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-17 22:15:22 (10298) [INFO] * free 0 * 2025-08-17 22:15:22 (10298) [INFO] * needed 100 k * 2025-08-17 22:15:22 (10315) [INFO] * 2025-08-17 22:15:22 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-17 22:15:22 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-17 22:15:22 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-17 22:15:22 (10285) [INFO] * 2025-08-17 22:15:23 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 22:15:23 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-17 22:15:23 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-17 22:15:23 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-17 22:15:23 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-17 22:15:23 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-17 22:15:23 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-17 22:15:23 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-17 22:15:23 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-17 22:15:23 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-17 22:15:23 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-17 22:15:23 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-17 22:15:23 (10315) [INFO] * 2025-08-17 22:15:23 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-17 22:15:23 (10285) [INFO] * 2025-08-17 22:15:23 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-17 22:15:23 (10298) [INFO] Determining fastest mirrors * 2025-08-17 22:15:27 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-17 22:15:27 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-17 22:15:27 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-17 22:15:27 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-17 22:15:27 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-17 22:15:27 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-17 22:15:27 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-17 22:15:27 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-17 22:15:27 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-17 22:15:27 (10298) [INFO] yum --disablerepo= ... * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-17 22:15:27 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-17 22:15:27 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] yum-config-manager --disable * 2025-08-17 22:15:27 (10298) [INFO] or * 2025-08-17 22:15:27 (10298) [INFO] subscription-manager repos --disable= * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-17 22:15:27 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-17 22:15:27 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-17 22:15:27 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-17 22:15:27 (10298) [INFO] compromise: * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-17 22:15:27 (10298) [INFO] * 2025-08-17 22:15:27 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-17 22:15:27 (10298) [INFO] * free 0 * 2025-08-17 22:15:27 (10298) [INFO] * needed 100 k * 2025-08-17 22:15:27 (10315) [INFO] * 2025-08-17 22:15:27 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-17 22:15:27 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-17 22:15:27 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-17 22:15:28 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wHjbPwOHry/ea_profile.json * 2025-08-17 22:15:29 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wHjbPwOHry/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-17 22:15:29 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-18 22:13:39 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-18 22:13:40 (11370) [INFO] Script is up to date. * 2025-08-18 22:13:41 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-18 22:13:41 (10285) [INFO] * 2025-08-18 22:14:36 (10315) [INFO] * 2025-08-18 22:14:36 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-18 22:14:36 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-18 22:14:36 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-18 22:14:36 (10285) [INFO] * 2025-08-18 22:14:39 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-18 22:14:39 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-18 22:14:39 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-18 22:14:39 (10285) [INFO] * 2025-08-18 22:14:44 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-18 22:14:44 (10285) [INFO] * 2025-08-18 22:14:44 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 22:14:44 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-18 22:14:45 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-18 22:14:45 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-18 22:14:45 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-18 22:14:45 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-18 22:14:45 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-18 22:14:45 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-18 22:14:45 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-18 22:14:45 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-18 22:14:45 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-18 22:14:45 (10298) [INFO] yum --disablerepo= ... * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-18 22:14:45 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-18 22:14:45 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] yum-config-manager --disable * 2025-08-18 22:14:45 (10298) [INFO] or * 2025-08-18 22:14:45 (10298) [INFO] subscription-manager repos --disable= * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-18 22:14:45 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-18 22:14:45 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-18 22:14:45 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-18 22:14:45 (10298) [INFO] compromise: * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-18 22:14:45 (10298) [INFO] * 2025-08-18 22:14:45 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-18 22:14:45 (10298) [INFO] * free 0 * 2025-08-18 22:14:45 (10298) [INFO] * needed 100 k * 2025-08-18 22:14:45 (10315) [INFO] * 2025-08-18 22:14:45 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-18 22:14:45 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-18 22:14:45 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-18 22:14:45 (10285) [INFO] * 2025-08-18 22:14:46 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 22:14:46 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-18 22:14:46 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-18 22:14:46 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-18 22:14:46 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-18 22:14:46 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-18 22:14:46 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-18 22:14:46 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-18 22:14:46 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-18 22:14:46 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-18 22:14:46 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-18 22:14:46 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-18 22:14:46 (10315) [INFO] * 2025-08-18 22:14:46 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-18 22:14:46 (10285) [INFO] * 2025-08-18 22:14:46 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-18 22:14:46 (10298) [INFO] Determining fastest mirrors * 2025-08-18 22:14:49 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-18 22:14:49 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-18 22:14:49 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-18 22:14:49 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-18 22:14:49 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-18 22:14:49 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-18 22:14:49 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-18 22:14:49 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-18 22:14:49 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-18 22:14:49 (10298) [INFO] yum --disablerepo= ... * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-18 22:14:49 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-18 22:14:49 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] yum-config-manager --disable * 2025-08-18 22:14:49 (10298) [INFO] or * 2025-08-18 22:14:49 (10298) [INFO] subscription-manager repos --disable= * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-18 22:14:49 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-18 22:14:49 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-18 22:14:49 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-18 22:14:49 (10298) [INFO] compromise: * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-18 22:14:49 (10298) [INFO] * 2025-08-18 22:14:49 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-18 22:14:49 (10298) [INFO] * free 0 * 2025-08-18 22:14:49 (10298) [INFO] * needed 100 k * 2025-08-18 22:14:49 (10315) [INFO] * 2025-08-18 22:14:49 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-18 22:14:49 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-18 22:14:49 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-18 22:14:50 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hYePeivA6q/ea_profile.json * 2025-08-18 22:14:51 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hYePeivA6q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-18 22:14:51 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-19 22:13:47 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-19 22:13:47 (11370) [INFO] Script is up to date. * 2025-08-19 22:13:48 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-19 22:13:48 (10285) [INFO] * 2025-08-19 22:14:41 (10315) [INFO] * 2025-08-19 22:14:41 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-19 22:14:41 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-19 22:14:41 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-19 22:14:41 (10285) [INFO] * 2025-08-19 22:14:46 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-19 22:14:46 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-19 22:14:46 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-19 22:14:46 (10285) [INFO] * 2025-08-19 22:14:49 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-19 22:14:49 (10285) [INFO] * 2025-08-19 22:14:49 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 22:14:49 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-19 22:14:50 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-19 22:14:50 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-19 22:14:50 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-19 22:14:50 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-19 22:14:50 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-19 22:14:50 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-19 22:14:50 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-19 22:14:50 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-19 22:14:50 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-19 22:14:50 (10298) [INFO] yum --disablerepo= ... * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-19 22:14:50 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-19 22:14:50 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] yum-config-manager --disable * 2025-08-19 22:14:50 (10298) [INFO] or * 2025-08-19 22:14:50 (10298) [INFO] subscription-manager repos --disable= * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-19 22:14:50 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-19 22:14:50 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-19 22:14:50 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-19 22:14:50 (10298) [INFO] compromise: * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-19 22:14:50 (10298) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-19 22:14:50 (10298) [INFO] * free 0 * 2025-08-19 22:14:50 (10298) [INFO] * needed 100 k * 2025-08-19 22:14:50 (10315) [INFO] * 2025-08-19 22:14:50 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-19 22:14:50 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-19 22:14:50 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-19 22:14:50 (10285) [INFO] * 2025-08-19 22:14:50 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 22:14:50 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-19 22:14:50 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-19 22:14:50 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-19 22:14:50 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-19 22:14:50 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-19 22:14:50 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-19 22:14:50 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-19 22:14:50 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-19 22:14:50 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-19 22:14:50 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-19 22:14:50 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-19 22:14:50 (10315) [INFO] * 2025-08-19 22:14:50 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-19 22:14:50 (10285) [INFO] * 2025-08-19 22:14:51 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-19 22:14:51 (10298) [INFO] Determining fastest mirrors * 2025-08-19 22:14:52 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-19 22:14:52 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-19 22:14:52 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-19 22:14:52 (10298) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-19 22:14:52 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-19 22:14:52 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-19 22:14:52 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-19 22:14:52 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-19 22:14:52 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-19 22:14:52 (10298) [INFO] yum --disablerepo= ... * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-19 22:14:52 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-19 22:14:52 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] yum-config-manager --disable * 2025-08-19 22:14:52 (10298) [INFO] or * 2025-08-19 22:14:52 (10298) [INFO] subscription-manager repos --disable= * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-19 22:14:52 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-19 22:14:52 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-19 22:14:52 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-19 22:14:52 (10298) [INFO] compromise: * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-19 22:14:52 (10298) [INFO] * 2025-08-19 22:14:52 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-19 22:14:52 (10298) [INFO] * free 0 * 2025-08-19 22:14:52 (10298) [INFO] * needed 100 k * 2025-08-19 22:14:52 (10315) [INFO] * 2025-08-19 22:14:52 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-19 22:14:52 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-19 22:14:52 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-19 22:14:53 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YnlmkUbYOy/ea_profile.json * 2025-08-19 22:14:54 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YnlmkUbYOy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-19 22:14:54 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-21 22:13:54 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-21 22:13:54 (11370) [INFO] Script is up to date. * 2025-08-21 22:13:55 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-21 22:13:55 (10285) [INFO] * 2025-08-21 22:14:46 (10315) [INFO] * 2025-08-21 22:14:46 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-21 22:14:46 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.70. * 2025-08-21 22:14:46 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-21 22:14:46 (10285) [INFO] * 2025-08-21 22:14:53 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-21 22:14:53 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-21 22:14:53 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-21 22:14:53 (10285) [INFO] * 2025-08-21 22:14:57 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-21 22:14:57 (10285) [INFO] * 2025-08-21 22:14:57 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 22:14:58 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-21 22:14:59 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-21 22:14:59 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-21 22:14:59 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-21 22:14:59 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-21 22:14:59 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-21 22:14:59 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-21 22:14:59 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-21 22:14:59 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-21 22:14:59 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-21 22:14:59 (10298) [INFO] yum --disablerepo= ... * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-21 22:14:59 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-21 22:14:59 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] yum-config-manager --disable * 2025-08-21 22:14:59 (10298) [INFO] or * 2025-08-21 22:14:59 (10298) [INFO] subscription-manager repos --disable= * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-21 22:14:59 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-21 22:14:59 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-21 22:14:59 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-21 22:14:59 (10298) [INFO] compromise: * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-21 22:14:59 (10298) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-21 22:14:59 (10298) [INFO] * free 0 * 2025-08-21 22:14:59 (10298) [INFO] * needed 100 k * 2025-08-21 22:14:59 (10315) [INFO] * 2025-08-21 22:14:59 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-21 22:14:59 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-21 22:14:59 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-21 22:14:59 (10285) [INFO] * 2025-08-21 22:14:59 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 22:14:59 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-21 22:14:59 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-21 22:14:59 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-21 22:14:59 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-21 22:14:59 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-21 22:14:59 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-21 22:14:59 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-21 22:14:59 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-21 22:14:59 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-21 22:15:00 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-21 22:15:00 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-21 22:15:00 (10315) [INFO] * 2025-08-21 22:15:00 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-21 22:15:00 (10285) [INFO] * 2025-08-21 22:15:00 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-21 22:15:00 (10298) [INFO] Determining fastest mirrors * 2025-08-21 22:15:04 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-21 22:15:04 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-21 22:15:04 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-21 22:15:04 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-21 22:15:04 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-21 22:15:04 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-21 22:15:04 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-21 22:15:04 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-21 22:15:04 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-21 22:15:04 (10298) [INFO] yum --disablerepo= ... * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-21 22:15:04 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-21 22:15:04 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] yum-config-manager --disable * 2025-08-21 22:15:04 (10298) [INFO] or * 2025-08-21 22:15:04 (10298) [INFO] subscription-manager repos --disable= * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-21 22:15:04 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-21 22:15:04 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-21 22:15:04 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-21 22:15:04 (10298) [INFO] compromise: * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-21 22:15:04 (10298) [INFO] * 2025-08-21 22:15:04 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-21 22:15:04 (10298) [INFO] * free 0 * 2025-08-21 22:15:04 (10298) [INFO] * needed 100 k * 2025-08-21 22:15:04 (10315) [INFO] * 2025-08-21 22:15:04 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-21 22:15:04 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-21 22:15:04 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-21 22:15:05 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mnbqklM4II/ea_profile.json * 2025-08-21 22:15:06 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mnbqklM4II/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-21 22:15:06 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-23 22:14:26 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-23 22:14:26 (11370) [INFO] Script is up to date. * 2025-08-23 22:14:28 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-23 22:14:28 (10285) [INFO] * 2025-08-23 22:15:10 (10315) [INFO] * 2025-08-23 22:15:10 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-23 22:15:10 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-23 22:15:10 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-23 22:15:10 (10285) [INFO] * 2025-08-23 22:15:15 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-23 22:15:15 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-23 22:15:15 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-23 22:15:15 (10285) [INFO] * 2025-08-23 22:15:20 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-23 22:15:20 (10285) [INFO] * 2025-08-23 22:15:20 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 22:15:20 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-23 22:15:22 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-23 22:15:22 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-23 22:15:22 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-23 22:15:22 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-23 22:15:22 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-23 22:15:22 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-23 22:15:22 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-23 22:15:22 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-23 22:15:22 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-23 22:15:22 (10298) [INFO] yum --disablerepo= ... * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-23 22:15:22 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-23 22:15:22 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] yum-config-manager --disable * 2025-08-23 22:15:22 (10298) [INFO] or * 2025-08-23 22:15:22 (10298) [INFO] subscription-manager repos --disable= * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-23 22:15:22 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-23 22:15:22 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-23 22:15:22 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-23 22:15:22 (10298) [INFO] compromise: * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-23 22:15:22 (10298) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-23 22:15:22 (10298) [INFO] * free 0 * 2025-08-23 22:15:22 (10298) [INFO] * needed 100 k * 2025-08-23 22:15:22 (10315) [INFO] * 2025-08-23 22:15:22 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-23 22:15:22 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-23 22:15:22 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-23 22:15:22 (10285) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 22:15:22 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-23 22:15:22 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-23 22:15:22 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-23 22:15:22 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-23 22:15:22 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-23 22:15:22 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-23 22:15:22 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-23 22:15:22 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-23 22:15:22 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-23 22:15:22 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-23 22:15:22 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-23 22:15:22 (10315) [INFO] * 2025-08-23 22:15:22 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-23 22:15:22 (10285) [INFO] * 2025-08-23 22:15:22 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-23 22:15:22 (10298) [INFO] Determining fastest mirrors * 2025-08-23 22:15:25 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-23 22:15:25 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-23 22:15:25 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-23 22:15:25 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-23 22:15:25 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-23 22:15:25 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-23 22:15:25 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-23 22:15:25 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-23 22:15:25 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-23 22:15:25 (10298) [INFO] yum --disablerepo= ... * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-23 22:15:25 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-23 22:15:25 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] yum-config-manager --disable * 2025-08-23 22:15:25 (10298) [INFO] or * 2025-08-23 22:15:25 (10298) [INFO] subscription-manager repos --disable= * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-23 22:15:25 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-23 22:15:25 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-23 22:15:25 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-23 22:15:25 (10298) [INFO] compromise: * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-23 22:15:25 (10298) [INFO] * 2025-08-23 22:15:25 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-23 22:15:25 (10298) [INFO] * free 0 * 2025-08-23 22:15:25 (10298) [INFO] * needed 100 k * 2025-08-23 22:15:25 (10315) [INFO] * 2025-08-23 22:15:25 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-23 22:15:25 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-23 22:15:26 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-23 22:15:27 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Te0L6Kd1tX/ea_profile.json * 2025-08-23 22:15:27 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Te0L6Kd1tX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-23 22:15:27 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-24 22:14:32 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-24 22:14:32 (11370) [INFO] Script is up to date. * 2025-08-24 22:14:34 (10284) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-24 22:14:34 (10285) [INFO] * 2025-08-24 22:15:34 (10315) [INFO] * 2025-08-24 22:15:34 (261) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-24 22:15:34 (261) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-24 22:15:34 (10284) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-24 22:15:34 (10285) [INFO] * 2025-08-24 22:15:37 (4382) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-24 22:15:37 (4389) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-24 22:15:37 (10284) [INFO] Running: /usr/bin/yum list extras * 2025-08-24 22:15:37 (10285) [INFO] * 2025-08-24 22:15:42 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-24 22:15:42 (10285) [INFO] * 2025-08-24 22:15:42 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 22:15:42 (10298) [INFO] Loading mirror speeds from cached hostfile * 2025-08-24 22:15:43 (10298) [INFO] * EA4: 91.99.144.170 * 2025-08-24 22:15:43 (10298) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-24 22:15:43 (10298) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-24 22:15:43 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-24 22:15:43 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-24 22:15:43 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-24 22:15:43 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-24 22:15:43 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-24 22:15:43 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-24 22:15:43 (10298) [INFO] yum --disablerepo= ... * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-24 22:15:43 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-24 22:15:43 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] yum-config-manager --disable * 2025-08-24 22:15:43 (10298) [INFO] or * 2025-08-24 22:15:43 (10298) [INFO] subscription-manager repos --disable= * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-24 22:15:43 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-24 22:15:43 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-24 22:15:43 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-24 22:15:43 (10298) [INFO] compromise: * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-24 22:15:43 (10298) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-24 22:15:43 (10298) [INFO] * free 0 * 2025-08-24 22:15:43 (10298) [INFO] * needed 100 k * 2025-08-24 22:15:43 (10315) [INFO] * 2025-08-24 22:15:43 (6383) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-24 22:15:43 (6384) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-24 22:15:43 (10284) [INFO] Running: /usr/bin/yum clean all * 2025-08-24 22:15:43 (10285) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 22:15:43 (10298) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-24 22:15:43 (10298) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-24 22:15:43 (10298) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-24 22:15:43 (10298) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-24 22:15:43 (10298) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-24 22:15:43 (10298) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-24 22:15:43 (10298) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-24 22:15:43 (10298) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-24 22:15:43 (10298) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-24 22:15:43 (10298) [INFO] Cleaning up list of fastest mirrors * 2025-08-24 22:15:43 (10298) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-24 22:15:43 (10315) [INFO] * 2025-08-24 22:15:43 (10284) [INFO] Running: /usr/bin/yum makecache * 2025-08-24 22:15:43 (10285) [INFO] * 2025-08-24 22:15:43 (10298) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-24 22:15:43 (10298) [INFO] Determining fastest mirrors * 2025-08-24 22:15:45 (10298) [INFO] * EA4: 188.245.60.65 * 2025-08-24 22:15:45 (10298) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-24 22:15:45 (10298) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-24 22:15:45 (10298) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] One of the configured repositories failed (Unknown), * 2025-08-24 22:15:45 (10298) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-24 22:15:45 (10298) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-24 22:15:45 (10298) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-24 22:15:45 (10298) [INFO] distribution release than is supported by the repository (and the * 2025-08-24 22:15:45 (10298) [INFO] packages for the previous distribution release still work). * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-24 22:15:45 (10298) [INFO] yum --disablerepo= ... * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-24 22:15:45 (10298) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-24 22:15:45 (10298) [INFO] again or use --enablerepo for temporary usage: * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] yum-config-manager --disable * 2025-08-24 22:15:45 (10298) [INFO] or * 2025-08-24 22:15:45 (10298) [INFO] subscription-manager repos --disable= * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-24 22:15:45 (10298) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-24 22:15:45 (10298) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-24 22:15:45 (10298) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-24 22:15:45 (10298) [INFO] compromise: * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-24 22:15:45 (10298) [INFO] * 2025-08-24 22:15:45 (10298) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-24 22:15:45 (10298) [INFO] * free 0 * 2025-08-24 22:15:45 (10298) [INFO] * needed 100 k * 2025-08-24 22:15:45 (10315) [INFO] * 2025-08-24 22:15:45 (6393) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-24 22:15:45 (6394) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-24 22:15:46 (2297) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-24 22:15:47 (9404) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P87VGzsSyd/ea_profile.json * 2025-08-24 22:15:47 (537) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P87VGzsSyd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9406. * 2025-08-24 22:15:47 (478) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-25 22:13:48 (11348) [INFO] Self-update of script version 69 requested. * 2025-08-25 22:13:48 (11353) [INFO] Newer version of script found. Downloading. * 2025-08-25 22:13:48 (11362) [INFO] Script update to version 70 successful. * 2025-08-25 22:13:50 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-25 22:13:50 (10381) [INFO] * 2025-08-25 22:14:53 (10411) [INFO] * 2025-08-25 22:14:53 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-25 22:14:53 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-25 22:14:53 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-25 22:14:53 (10381) [INFO] * 2025-08-25 22:14:58 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-25 22:14:58 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-25 22:14:58 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-25 22:14:58 (10381) [INFO] * 2025-08-25 22:15:02 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-25 22:15:02 (10381) [INFO] * 2025-08-25 22:15:02 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 22:15:02 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-25 22:15:03 (10394) [INFO] * EA4: 188.245.60.65 * 2025-08-25 22:15:03 (10394) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-25 22:15:03 (10394) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-25 22:15:03 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-25 22:15:03 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-25 22:15:03 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-25 22:15:03 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-25 22:15:03 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-25 22:15:03 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-25 22:15:03 (10394) [INFO] yum --disablerepo= ... * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-25 22:15:03 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-25 22:15:03 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] yum-config-manager --disable * 2025-08-25 22:15:03 (10394) [INFO] or * 2025-08-25 22:15:03 (10394) [INFO] subscription-manager repos --disable= * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-25 22:15:03 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-25 22:15:03 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-25 22:15:03 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-25 22:15:03 (10394) [INFO] compromise: * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-25 22:15:03 (10394) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-25 22:15:03 (10394) [INFO] * free 0 * 2025-08-25 22:15:03 (10394) [INFO] * needed 100 k * 2025-08-25 22:15:03 (10411) [INFO] * 2025-08-25 22:15:03 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-25 22:15:03 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-25 22:15:03 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-25 22:15:03 (10381) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 22:15:03 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-25 22:15:03 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-25 22:15:03 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-25 22:15:03 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-25 22:15:03 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-25 22:15:03 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-25 22:15:03 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-25 22:15:03 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-25 22:15:03 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-25 22:15:03 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-25 22:15:03 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-25 22:15:03 (10411) [INFO] * 2025-08-25 22:15:03 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-25 22:15:03 (10381) [INFO] * 2025-08-25 22:15:03 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-25 22:15:04 (10394) [INFO] Determining fastest mirrors * 2025-08-25 22:15:06 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-25 22:15:06 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-25 22:15:06 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-25 22:15:06 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-25 22:15:06 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-25 22:15:06 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-25 22:15:06 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-25 22:15:06 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-25 22:15:06 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-25 22:15:06 (10394) [INFO] yum --disablerepo= ... * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-25 22:15:06 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-25 22:15:06 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] yum-config-manager --disable * 2025-08-25 22:15:06 (10394) [INFO] or * 2025-08-25 22:15:06 (10394) [INFO] subscription-manager repos --disable= * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-25 22:15:06 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-25 22:15:06 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-25 22:15:06 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-25 22:15:06 (10394) [INFO] compromise: * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-25 22:15:06 (10394) [INFO] * 2025-08-25 22:15:06 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-25 22:15:06 (10394) [INFO] * free 0 * 2025-08-25 22:15:06 (10394) [INFO] * needed 100 k * 2025-08-25 22:15:06 (10411) [INFO] * 2025-08-25 22:15:06 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-25 22:15:06 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-25 22:15:07 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-25 22:15:08 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iO9AOqUaXd/ea_profile.json * 2025-08-25 22:15:08 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iO9AOqUaXd/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-25 22:15:08 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-28 22:13:40 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-28 22:13:40 (11467) [INFO] Script is up to date. * 2025-08-28 22:13:41 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-28 22:13:41 (10381) [INFO] * 2025-08-28 22:14:19 (10411) [INFO] * 2025-08-28 22:14:19 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-28 22:14:19 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-28 22:14:19 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-28 22:14:19 (10381) [INFO] * 2025-08-28 22:14:22 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-28 22:14:22 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-28 22:14:22 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-28 22:14:22 (10381) [INFO] * 2025-08-28 22:14:24 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-28 22:14:24 (10381) [INFO] * 2025-08-28 22:14:25 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 22:14:25 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-28 22:14:26 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-28 22:14:26 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-28 22:14:26 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-28 22:14:26 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-28 22:14:26 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-28 22:14:26 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-28 22:14:26 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-28 22:14:26 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-28 22:14:26 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-28 22:14:26 (10394) [INFO] yum --disablerepo= ... * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-28 22:14:26 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-28 22:14:26 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] yum-config-manager --disable * 2025-08-28 22:14:26 (10394) [INFO] or * 2025-08-28 22:14:26 (10394) [INFO] subscription-manager repos --disable= * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-28 22:14:26 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-28 22:14:26 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-28 22:14:26 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-28 22:14:26 (10394) [INFO] compromise: * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-28 22:14:26 (10394) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-28 22:14:26 (10394) [INFO] * free 0 * 2025-08-28 22:14:26 (10394) [INFO] * needed 100 k * 2025-08-28 22:14:26 (10411) [INFO] * 2025-08-28 22:14:26 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-28 22:14:26 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-28 22:14:26 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-28 22:14:26 (10381) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 22:14:26 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-28 22:14:26 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-28 22:14:26 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-28 22:14:26 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-28 22:14:26 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-28 22:14:26 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-28 22:14:26 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-28 22:14:26 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-28 22:14:26 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-28 22:14:26 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-28 22:14:26 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-28 22:14:26 (10411) [INFO] * 2025-08-28 22:14:26 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-28 22:14:26 (10381) [INFO] * 2025-08-28 22:14:26 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-28 22:14:26 (10394) [INFO] Determining fastest mirrors * 2025-08-28 22:14:29 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-28 22:14:29 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-28 22:14:29 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-28 22:14:29 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-28 22:14:29 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-28 22:14:29 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-28 22:14:29 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-28 22:14:29 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-28 22:14:29 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-28 22:14:29 (10394) [INFO] yum --disablerepo= ... * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-28 22:14:29 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-28 22:14:29 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] yum-config-manager --disable * 2025-08-28 22:14:29 (10394) [INFO] or * 2025-08-28 22:14:29 (10394) [INFO] subscription-manager repos --disable= * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-28 22:14:29 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-28 22:14:29 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-28 22:14:29 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-28 22:14:29 (10394) [INFO] compromise: * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-28 22:14:29 (10394) [INFO] * 2025-08-28 22:14:29 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-28 22:14:29 (10394) [INFO] * free 0 * 2025-08-28 22:14:29 (10394) [INFO] * needed 100 k * 2025-08-28 22:14:29 (10411) [INFO] * 2025-08-28 22:14:29 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-28 22:14:29 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-28 22:14:29 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-28 22:14:30 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zqoqkTYs7k/ea_profile.json * 2025-08-28 22:14:30 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zqoqkTYs7k/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-28 22:14:30 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-29 22:13:49 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-29 22:13:49 (11467) [INFO] Script is up to date. * 2025-08-29 22:13:51 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-29 22:13:51 (10381) [INFO] * 2025-08-29 22:14:41 (10411) [INFO] * 2025-08-29 22:14:41 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-29 22:14:41 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-29 22:14:41 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-29 22:14:41 (10381) [INFO] * 2025-08-29 22:14:46 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-29 22:14:46 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-29 22:14:46 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-29 22:14:46 (10381) [INFO] * 2025-08-29 22:14:52 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-29 22:14:52 (10381) [INFO] * 2025-08-29 22:14:52 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 22:14:52 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-29 22:14:55 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-29 22:14:55 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-29 22:14:55 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-29 22:14:55 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-29 22:14:55 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-29 22:14:55 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-29 22:14:55 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-29 22:14:55 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-29 22:14:55 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-29 22:14:55 (10394) [INFO] yum --disablerepo= ... * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-29 22:14:55 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-29 22:14:55 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] yum-config-manager --disable * 2025-08-29 22:14:55 (10394) [INFO] or * 2025-08-29 22:14:55 (10394) [INFO] subscription-manager repos --disable= * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-29 22:14:55 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-29 22:14:55 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-29 22:14:55 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-29 22:14:55 (10394) [INFO] compromise: * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-29 22:14:55 (10394) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-29 22:14:55 (10394) [INFO] * free 0 * 2025-08-29 22:14:55 (10394) [INFO] * needed 100 k * 2025-08-29 22:14:55 (10411) [INFO] * 2025-08-29 22:14:55 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-29 22:14:55 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-29 22:14:55 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-29 22:14:55 (10381) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 22:14:55 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-29 22:14:55 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-29 22:14:55 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-29 22:14:55 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-29 22:14:55 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-29 22:14:55 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-29 22:14:55 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-29 22:14:55 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-29 22:14:55 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-29 22:14:55 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-29 22:14:55 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-29 22:14:55 (10411) [INFO] * 2025-08-29 22:14:55 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-29 22:14:55 (10381) [INFO] * 2025-08-29 22:14:55 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-29 22:14:56 (10394) [INFO] Determining fastest mirrors * 2025-08-29 22:14:58 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-29 22:14:58 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-29 22:14:58 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-29 22:14:58 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-29 22:14:58 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-29 22:14:58 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-29 22:14:58 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-29 22:14:58 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-29 22:14:58 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-29 22:14:58 (10394) [INFO] yum --disablerepo= ... * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-29 22:14:58 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-29 22:14:58 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] yum-config-manager --disable * 2025-08-29 22:14:58 (10394) [INFO] or * 2025-08-29 22:14:58 (10394) [INFO] subscription-manager repos --disable= * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-29 22:14:58 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-29 22:14:58 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-29 22:14:58 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-29 22:14:58 (10394) [INFO] compromise: * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-29 22:14:58 (10394) [INFO] * 2025-08-29 22:14:58 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-29 22:14:58 (10394) [INFO] * free 0 * 2025-08-29 22:14:58 (10394) [INFO] * needed 100 k * 2025-08-29 22:14:58 (10411) [INFO] * 2025-08-29 22:14:58 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-29 22:14:58 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-29 22:14:59 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-29 22:15:00 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C57IDNgEbc/ea_profile.json * 2025-08-29 22:15:01 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C57IDNgEbc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-29 22:15:01 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-30 22:14:30 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-30 22:14:30 (11467) [INFO] Script is up to date. * 2025-08-30 22:14:32 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-30 22:14:32 (10381) [INFO] * 2025-08-30 22:15:18 (10411) [INFO] * 2025-08-30 22:15:18 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-30 22:15:18 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-30 22:15:18 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-30 22:15:18 (10381) [INFO] * 2025-08-30 22:15:23 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-30 22:15:23 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-30 22:15:23 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-30 22:15:23 (10381) [INFO] * 2025-08-30 22:15:34 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-30 22:15:34 (10381) [INFO] * 2025-08-30 22:15:34 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 22:15:34 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-30 22:15:43 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-30 22:15:43 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-30 22:15:43 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-30 22:15:43 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-30 22:15:43 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-30 22:15:43 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-30 22:15:43 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-30 22:15:43 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-30 22:15:43 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-30 22:15:43 (10394) [INFO] yum --disablerepo= ... * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-30 22:15:43 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-30 22:15:43 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] yum-config-manager --disable * 2025-08-30 22:15:43 (10394) [INFO] or * 2025-08-30 22:15:43 (10394) [INFO] subscription-manager repos --disable= * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-30 22:15:43 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-30 22:15:43 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-30 22:15:43 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-30 22:15:43 (10394) [INFO] compromise: * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-30 22:15:43 (10394) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-30 22:15:43 (10394) [INFO] * free 0 * 2025-08-30 22:15:43 (10394) [INFO] * needed 100 k * 2025-08-30 22:15:43 (10411) [INFO] * 2025-08-30 22:15:43 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-30 22:15:43 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-30 22:15:43 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-30 22:15:43 (10381) [INFO] * 2025-08-30 22:15:43 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 22:15:44 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-30 22:15:44 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-30 22:15:44 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-30 22:15:44 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-30 22:15:44 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-30 22:15:44 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-30 22:15:44 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-30 22:15:44 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-30 22:15:44 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-30 22:15:44 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-30 22:15:44 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-30 22:15:44 (10411) [INFO] * 2025-08-30 22:15:44 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-30 22:15:44 (10381) [INFO] * 2025-08-30 22:15:44 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-30 22:15:44 (10394) [INFO] Determining fastest mirrors * 2025-08-30 22:15:46 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-30 22:15:46 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-30 22:15:46 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-30 22:15:46 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-30 22:15:46 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-30 22:15:46 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-30 22:15:46 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-30 22:15:46 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-30 22:15:46 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-30 22:15:46 (10394) [INFO] yum --disablerepo= ... * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-30 22:15:46 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-30 22:15:46 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] yum-config-manager --disable * 2025-08-30 22:15:46 (10394) [INFO] or * 2025-08-30 22:15:46 (10394) [INFO] subscription-manager repos --disable= * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-30 22:15:46 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-30 22:15:46 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-30 22:15:46 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-30 22:15:46 (10394) [INFO] compromise: * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-30 22:15:46 (10394) [INFO] * 2025-08-30 22:15:46 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-30 22:15:46 (10394) [INFO] * free 0 * 2025-08-30 22:15:46 (10394) [INFO] * needed 100 k * 2025-08-30 22:15:46 (10411) [INFO] * 2025-08-30 22:15:46 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-30 22:15:46 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-30 22:15:47 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-30 22:15:47 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZxGK9tbPqY/ea_profile.json * 2025-08-30 22:15:48 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZxGK9tbPqY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-30 22:15:48 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-08-31 22:14:31 (11445) [INFO] Self-update of script version 70 requested. * 2025-08-31 22:14:31 (11467) [INFO] Script is up to date. * 2025-08-31 22:14:33 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-08-31 22:14:33 (10381) [INFO] * 2025-08-31 22:15:14 (10411) [INFO] * 2025-08-31 22:15:14 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-08-31 22:15:14 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-08-31 22:15:14 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-08-31 22:15:14 (10381) [INFO] * 2025-08-31 22:15:17 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-08-31 22:15:17 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-08-31 22:15:17 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-08-31 22:15:17 (10381) [INFO] * 2025-08-31 22:15:22 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-31 22:15:22 (10381) [INFO] * 2025-08-31 22:15:22 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 22:15:22 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-08-31 22:15:23 (10394) [INFO] * EA4: 91.99.144.170 * 2025-08-31 22:15:23 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-08-31 22:15:23 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-08-31 22:15:23 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-31 22:15:23 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-31 22:15:23 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-31 22:15:23 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-31 22:15:23 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-31 22:15:23 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-31 22:15:23 (10394) [INFO] yum --disablerepo= ... * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-31 22:15:23 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-31 22:15:23 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] yum-config-manager --disable * 2025-08-31 22:15:23 (10394) [INFO] or * 2025-08-31 22:15:23 (10394) [INFO] subscription-manager repos --disable= * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-31 22:15:23 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-31 22:15:23 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-31 22:15:23 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-31 22:15:23 (10394) [INFO] compromise: * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-31 22:15:23 (10394) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-31 22:15:23 (10394) [INFO] * free 0 * 2025-08-31 22:15:23 (10394) [INFO] * needed 100 k * 2025-08-31 22:15:23 (10411) [INFO] * 2025-08-31 22:15:23 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-31 22:15:23 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-08-31 22:15:23 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-08-31 22:15:23 (10381) [INFO] * 2025-08-31 22:15:23 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 22:15:23 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-08-31 22:15:23 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-08-31 22:15:23 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-08-31 22:15:23 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-08-31 22:15:23 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-08-31 22:15:23 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-08-31 22:15:23 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-08-31 22:15:23 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-08-31 22:15:23 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-08-31 22:15:23 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-08-31 22:15:23 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-08-31 22:15:23 (10411) [INFO] * 2025-08-31 22:15:23 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-08-31 22:15:23 (10381) [INFO] * 2025-08-31 22:15:24 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-08-31 22:15:24 (10394) [INFO] Determining fastest mirrors * 2025-08-31 22:15:26 (10394) [INFO] * EA4: 188.245.60.65 * 2025-08-31 22:15:26 (10394) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-08-31 22:15:26 (10394) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-08-31 22:15:26 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-08-31 22:15:26 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-08-31 22:15:26 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-08-31 22:15:26 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-08-31 22:15:26 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-08-31 22:15:26 (10394) [INFO] packages for the previous distribution release still work). * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-08-31 22:15:26 (10394) [INFO] yum --disablerepo= ... * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-08-31 22:15:26 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-08-31 22:15:26 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] yum-config-manager --disable * 2025-08-31 22:15:26 (10394) [INFO] or * 2025-08-31 22:15:26 (10394) [INFO] subscription-manager repos --disable= * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-08-31 22:15:26 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-08-31 22:15:26 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-08-31 22:15:26 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-08-31 22:15:26 (10394) [INFO] compromise: * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-08-31 22:15:26 (10394) [INFO] * 2025-08-31 22:15:26 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-08-31 22:15:26 (10394) [INFO] * free 0 * 2025-08-31 22:15:26 (10394) [INFO] * needed 100 k * 2025-08-31 22:15:26 (10411) [INFO] * 2025-08-31 22:15:26 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-08-31 22:15:26 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-08-31 22:15:27 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-08-31 22:15:27 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L89W41kJt8/ea_profile.json * 2025-08-31 22:15:28 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L89W41kJt8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-08-31 22:15:28 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-01 22:13:43 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-01 22:13:43 (11467) [INFO] Script is up to date. * 2025-09-01 22:13:45 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-01 22:13:45 (10381) [INFO] * 2025-09-01 22:14:36 (10411) [INFO] * 2025-09-01 22:14:36 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-01 22:14:36 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-01 22:14:36 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-01 22:14:36 (10381) [INFO] * 2025-09-01 22:14:40 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-01 22:14:40 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-01 22:14:40 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-01 22:14:40 (10381) [INFO] * 2025-09-01 22:14:45 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-01 22:14:45 (10381) [INFO] * 2025-09-01 22:14:45 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 22:14:45 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-01 22:14:46 (10394) [INFO] * EA4: 91.99.144.170 * 2025-09-01 22:14:46 (10394) [INFO] * cpanel-addons-production-feed: 91.99.144.170 * 2025-09-01 22:14:46 (10394) [INFO] * cpanel-plugins: 91.99.144.170 * 2025-09-01 22:14:46 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-01 22:14:46 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-01 22:14:46 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-01 22:14:46 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-01 22:14:46 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-01 22:14:46 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-01 22:14:46 (10394) [INFO] yum --disablerepo= ... * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-01 22:14:46 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-01 22:14:46 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] yum-config-manager --disable * 2025-09-01 22:14:46 (10394) [INFO] or * 2025-09-01 22:14:46 (10394) [INFO] subscription-manager repos --disable= * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-01 22:14:46 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-01 22:14:46 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-01 22:14:46 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-01 22:14:46 (10394) [INFO] compromise: * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-01 22:14:46 (10394) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-01 22:14:46 (10394) [INFO] * free 0 * 2025-09-01 22:14:46 (10394) [INFO] * needed 100 k * 2025-09-01 22:14:46 (10411) [INFO] * 2025-09-01 22:14:46 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-01 22:14:46 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-01 22:14:46 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-01 22:14:46 (10381) [INFO] * 2025-09-01 22:14:46 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 22:14:46 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-01 22:14:46 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-01 22:14:46 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-01 22:14:46 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-01 22:14:46 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-01 22:14:46 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-01 22:14:46 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-01 22:14:46 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-01 22:14:46 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-01 22:14:46 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-01 22:14:46 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-01 22:14:46 (10411) [INFO] * 2025-09-01 22:14:46 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-01 22:14:46 (10381) [INFO] * 2025-09-01 22:14:47 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-01 22:14:47 (10394) [INFO] Determining fastest mirrors * 2025-09-01 22:14:48 (10394) [INFO] * EA4: 188.245.60.65 * 2025-09-01 22:14:49 (10394) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-09-01 22:14:49 (10394) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-09-01 22:14:49 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-01 22:14:49 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-01 22:14:49 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-01 22:14:49 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-01 22:14:49 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-01 22:14:49 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-01 22:14:49 (10394) [INFO] yum --disablerepo= ... * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-01 22:14:49 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-01 22:14:49 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] yum-config-manager --disable * 2025-09-01 22:14:49 (10394) [INFO] or * 2025-09-01 22:14:49 (10394) [INFO] subscription-manager repos --disable= * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-01 22:14:49 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-01 22:14:49 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-01 22:14:49 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-01 22:14:49 (10394) [INFO] compromise: * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-01 22:14:49 (10394) [INFO] * 2025-09-01 22:14:49 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-01 22:14:49 (10394) [INFO] * free 0 * 2025-09-01 22:14:49 (10394) [INFO] * needed 100 k * 2025-09-01 22:14:49 (10411) [INFO] * 2025-09-01 22:14:49 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-01 22:14:49 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-01 22:14:49 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-01 22:14:50 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dBHw8Wj7jj/ea_profile.json * 2025-09-01 22:14:50 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dBHw8Wj7jj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-01 22:14:50 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-02 22:13:43 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-02 22:13:43 (11467) [INFO] Script is up to date. * 2025-09-02 22:13:44 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-02 22:13:44 (10381) [INFO] * 2025-09-02 22:14:25 (10411) [INFO] * 2025-09-02 22:14:25 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-02 22:14:25 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-02 22:14:25 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-02 22:14:25 (10381) [INFO] * 2025-09-02 22:14:28 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-02 22:14:28 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-02 22:14:28 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-02 22:14:28 (10381) [INFO] * 2025-09-02 22:14:32 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-02 22:14:32 (10381) [INFO] * 2025-09-02 22:14:32 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 22:14:32 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-02 22:14:34 (10394) [INFO] * EA4: 188.245.60.65 * 2025-09-02 22:14:34 (10394) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-09-02 22:14:34 (10394) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-09-02 22:14:34 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-02 22:14:34 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-02 22:14:34 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-02 22:14:34 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-02 22:14:34 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-02 22:14:34 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-02 22:14:34 (10394) [INFO] yum --disablerepo= ... * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-02 22:14:34 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-02 22:14:34 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] yum-config-manager --disable * 2025-09-02 22:14:34 (10394) [INFO] or * 2025-09-02 22:14:34 (10394) [INFO] subscription-manager repos --disable= * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-02 22:14:34 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-02 22:14:34 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-02 22:14:34 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-02 22:14:34 (10394) [INFO] compromise: * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-02 22:14:34 (10394) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-02 22:14:34 (10394) [INFO] * free 0 * 2025-09-02 22:14:34 (10394) [INFO] * needed 100 k * 2025-09-02 22:14:34 (10411) [INFO] * 2025-09-02 22:14:34 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-02 22:14:34 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-02 22:14:34 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-02 22:14:34 (10381) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 22:14:34 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-02 22:14:34 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-02 22:14:34 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-02 22:14:34 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-02 22:14:34 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-02 22:14:34 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-02 22:14:34 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-02 22:14:34 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-02 22:14:34 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-02 22:14:34 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-02 22:14:34 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-02 22:14:34 (10411) [INFO] * 2025-09-02 22:14:34 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-02 22:14:34 (10381) [INFO] * 2025-09-02 22:14:34 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-02 22:14:34 (10394) [INFO] Determining fastest mirrors * 2025-09-02 22:14:37 (10394) [INFO] * EA4: 188.245.60.65 * 2025-09-02 22:14:37 (10394) [INFO] * cpanel-addons-production-feed: 188.245.60.65 * 2025-09-02 22:14:37 (10394) [INFO] * cpanel-plugins: 188.245.60.65 * 2025-09-02 22:14:37 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-02 22:14:37 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-02 22:14:37 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-02 22:14:37 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-02 22:14:37 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-02 22:14:37 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-02 22:14:37 (10394) [INFO] yum --disablerepo= ... * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-02 22:14:37 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-02 22:14:37 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] yum-config-manager --disable * 2025-09-02 22:14:37 (10394) [INFO] or * 2025-09-02 22:14:37 (10394) [INFO] subscription-manager repos --disable= * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-02 22:14:37 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-02 22:14:37 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-02 22:14:37 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-02 22:14:37 (10394) [INFO] compromise: * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-02 22:14:37 (10394) [INFO] * 2025-09-02 22:14:37 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-02 22:14:37 (10394) [INFO] * free 0 * 2025-09-02 22:14:37 (10394) [INFO] * needed 100 k * 2025-09-02 22:14:37 (10411) [INFO] * 2025-09-02 22:14:37 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-02 22:14:37 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-02 22:14:38 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-02 22:14:38 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jSf7nQmYsS/ea_profile.json * 2025-09-02 22:14:39 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jSf7nQmYsS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-02 22:14:39 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-03 22:13:39 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-03 22:13:40 (11467) [INFO] Script is up to date. * 2025-09-03 22:13:41 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-03 22:13:41 (10381) [INFO] * 2025-09-03 22:14:30 (10411) [INFO] * 2025-09-03 22:14:30 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-03 22:14:30 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-03 22:14:30 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-03 22:14:30 (10381) [INFO] * 2025-09-03 22:14:34 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-03 22:14:34 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-03 22:14:34 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-03 22:14:34 (10381) [INFO] * 2025-09-03 22:14:38 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-03 22:14:38 (10381) [INFO] * 2025-09-03 22:14:38 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 22:14:38 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-03 22:14:40 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-03 22:14:40 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-03 22:14:40 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-03 22:14:40 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-03 22:14:40 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-03 22:14:40 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-03 22:14:40 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-03 22:14:40 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-03 22:14:40 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-03 22:14:40 (10394) [INFO] yum --disablerepo= ... * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-03 22:14:40 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-03 22:14:40 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] yum-config-manager --disable * 2025-09-03 22:14:40 (10394) [INFO] or * 2025-09-03 22:14:40 (10394) [INFO] subscription-manager repos --disable= * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-03 22:14:40 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-03 22:14:40 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-03 22:14:40 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-03 22:14:40 (10394) [INFO] compromise: * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-03 22:14:40 (10394) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-03 22:14:40 (10394) [INFO] * free 0 * 2025-09-03 22:14:40 (10394) [INFO] * needed 100 k * 2025-09-03 22:14:40 (10411) [INFO] * 2025-09-03 22:14:40 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-03 22:14:40 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-03 22:14:40 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-03 22:14:40 (10381) [INFO] * 2025-09-03 22:14:40 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 22:14:41 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-03 22:14:41 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-03 22:14:41 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-03 22:14:41 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-03 22:14:41 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-03 22:14:41 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-03 22:14:41 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-03 22:14:41 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-03 22:14:41 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-03 22:14:41 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-03 22:14:41 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-03 22:14:41 (10411) [INFO] * 2025-09-03 22:14:41 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-03 22:14:41 (10381) [INFO] * 2025-09-03 22:14:41 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-03 22:14:41 (10394) [INFO] Determining fastest mirrors * 2025-09-03 22:14:45 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-03 22:14:45 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-03 22:14:45 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-03 22:14:45 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-03 22:14:45 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-03 22:14:45 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-03 22:14:45 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-03 22:14:45 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-03 22:14:45 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-03 22:14:45 (10394) [INFO] yum --disablerepo= ... * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-03 22:14:45 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-03 22:14:45 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] yum-config-manager --disable * 2025-09-03 22:14:45 (10394) [INFO] or * 2025-09-03 22:14:45 (10394) [INFO] subscription-manager repos --disable= * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-03 22:14:45 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-03 22:14:45 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-03 22:14:45 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-03 22:14:45 (10394) [INFO] compromise: * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-03 22:14:45 (10394) [INFO] * 2025-09-03 22:14:45 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-03 22:14:45 (10394) [INFO] * free 0 * 2025-09-03 22:14:45 (10394) [INFO] * needed 100 k * 2025-09-03 22:14:45 (10411) [INFO] * 2025-09-03 22:14:45 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-03 22:14:45 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-03 22:14:45 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-03 22:14:46 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OOgi2o99gX/ea_profile.json * 2025-09-03 22:14:47 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OOgi2o99gX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-03 22:14:47 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-04 22:13:43 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-04 22:13:44 (11467) [INFO] Script is up to date. * 2025-09-04 22:13:45 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-04 22:13:45 (10381) [INFO] * 2025-09-04 22:14:34 (10411) [INFO] * 2025-09-04 22:14:34 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-04 22:14:34 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-04 22:14:34 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-04 22:14:34 (10381) [INFO] * 2025-09-04 22:14:38 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-04 22:14:38 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-04 22:14:38 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-04 22:14:38 (10381) [INFO] * 2025-09-04 22:14:41 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-04 22:14:41 (10381) [INFO] * 2025-09-04 22:14:41 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 22:14:41 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-04 22:14:42 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-04 22:14:42 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-04 22:14:42 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-04 22:14:42 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-04 22:14:42 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-04 22:14:42 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-04 22:14:42 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-04 22:14:42 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-04 22:14:42 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-04 22:14:42 (10394) [INFO] yum --disablerepo= ... * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-04 22:14:42 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-04 22:14:42 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] yum-config-manager --disable * 2025-09-04 22:14:42 (10394) [INFO] or * 2025-09-04 22:14:42 (10394) [INFO] subscription-manager repos --disable= * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-04 22:14:42 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-04 22:14:42 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-04 22:14:42 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-04 22:14:42 (10394) [INFO] compromise: * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-04 22:14:42 (10394) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-04 22:14:42 (10394) [INFO] * free 0 * 2025-09-04 22:14:42 (10394) [INFO] * needed 100 k * 2025-09-04 22:14:42 (10411) [INFO] * 2025-09-04 22:14:42 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-04 22:14:42 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-04 22:14:42 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-04 22:14:42 (10381) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 22:14:42 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-04 22:14:42 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-04 22:14:42 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-04 22:14:42 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-04 22:14:42 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-04 22:14:42 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-04 22:14:42 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-04 22:14:42 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-04 22:14:42 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-04 22:14:42 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-04 22:14:42 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-04 22:14:42 (10411) [INFO] * 2025-09-04 22:14:42 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-04 22:14:42 (10381) [INFO] * 2025-09-04 22:14:42 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-04 22:14:42 (10394) [INFO] Determining fastest mirrors * 2025-09-04 22:14:44 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-04 22:14:44 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-04 22:14:44 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-04 22:14:44 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-04 22:14:44 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-04 22:14:44 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-04 22:14:44 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-04 22:14:44 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-04 22:14:44 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-04 22:14:44 (10394) [INFO] yum --disablerepo= ... * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-04 22:14:44 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-04 22:14:44 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] yum-config-manager --disable * 2025-09-04 22:14:44 (10394) [INFO] or * 2025-09-04 22:14:44 (10394) [INFO] subscription-manager repos --disable= * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-04 22:14:44 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-04 22:14:44 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-04 22:14:44 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-04 22:14:44 (10394) [INFO] compromise: * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-04 22:14:44 (10394) [INFO] * 2025-09-04 22:14:44 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-04 22:14:44 (10394) [INFO] * free 0 * 2025-09-04 22:14:44 (10394) [INFO] * needed 100 k * 2025-09-04 22:14:44 (10411) [INFO] * 2025-09-04 22:14:44 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-04 22:14:44 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-04 22:14:44 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-04 22:14:45 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/opuOAb4gzZ/ea_profile.json * 2025-09-04 22:14:45 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/opuOAb4gzZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-04 22:14:45 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-05 22:13:37 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-05 22:13:37 (11467) [INFO] Script is up to date. * 2025-09-05 22:13:38 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-05 22:13:38 (10381) [INFO] * 2025-09-05 22:14:14 (10411) [INFO] * 2025-09-05 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-05 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-05 22:14:14 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-05 22:14:14 (10381) [INFO] * 2025-09-05 22:14:17 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-05 22:14:17 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-05 22:14:17 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-05 22:14:17 (10381) [INFO] * 2025-09-05 22:14:19 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-05 22:14:19 (10381) [INFO] * 2025-09-05 22:14:19 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 22:14:19 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-05 22:14:20 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-05 22:14:20 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-05 22:14:20 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-05 22:14:20 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-05 22:14:20 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-05 22:14:20 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-05 22:14:20 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-05 22:14:20 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-05 22:14:20 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-05 22:14:20 (10394) [INFO] yum --disablerepo= ... * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-05 22:14:20 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-05 22:14:20 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] yum-config-manager --disable * 2025-09-05 22:14:20 (10394) [INFO] or * 2025-09-05 22:14:20 (10394) [INFO] subscription-manager repos --disable= * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-05 22:14:20 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-05 22:14:20 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-05 22:14:20 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-05 22:14:20 (10394) [INFO] compromise: * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-05 22:14:20 (10394) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-05 22:14:20 (10394) [INFO] * free 0 * 2025-09-05 22:14:20 (10394) [INFO] * needed 100 k * 2025-09-05 22:14:20 (10411) [INFO] * 2025-09-05 22:14:20 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-05 22:14:20 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-05 22:14:20 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-05 22:14:20 (10381) [INFO] * 2025-09-05 22:14:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 22:14:20 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-05 22:14:20 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-05 22:14:20 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-05 22:14:20 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-05 22:14:20 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-05 22:14:20 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-05 22:14:20 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-05 22:14:20 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-05 22:14:20 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-05 22:14:20 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-05 22:14:21 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-05 22:14:21 (10411) [INFO] * 2025-09-05 22:14:21 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-05 22:14:21 (10381) [INFO] * 2025-09-05 22:14:21 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-05 22:14:21 (10394) [INFO] Determining fastest mirrors * 2025-09-05 22:14:24 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-05 22:14:24 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-05 22:14:24 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-05 22:14:24 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-05 22:14:24 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-05 22:14:24 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-05 22:14:24 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-05 22:14:24 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-05 22:14:24 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-05 22:14:24 (10394) [INFO] yum --disablerepo= ... * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-05 22:14:24 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-05 22:14:24 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] yum-config-manager --disable * 2025-09-05 22:14:24 (10394) [INFO] or * 2025-09-05 22:14:24 (10394) [INFO] subscription-manager repos --disable= * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-05 22:14:24 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-05 22:14:24 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-05 22:14:24 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-05 22:14:24 (10394) [INFO] compromise: * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-05 22:14:24 (10394) [INFO] * 2025-09-05 22:14:24 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-05 22:14:24 (10394) [INFO] * free 0 * 2025-09-05 22:14:24 (10394) [INFO] * needed 100 k * 2025-09-05 22:14:24 (10411) [INFO] * 2025-09-05 22:14:24 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-05 22:14:24 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-05 22:14:24 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-05 22:14:25 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ewnHBYlaze/ea_profile.json * 2025-09-05 22:14:26 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ewnHBYlaze/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-05 22:14:26 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-06 22:14:11 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-06 22:14:12 (11467) [INFO] Script is up to date. * 2025-09-06 22:14:13 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-06 22:14:13 (10381) [INFO] * 2025-09-06 22:14:39 (10411) [INFO] * 2025-09-06 22:14:39 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-06 22:14:39 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-06 22:14:39 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-06 22:14:39 (10381) [INFO] * 2025-09-06 22:14:42 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-06 22:14:42 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-06 22:14:42 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-06 22:14:42 (10381) [INFO] * 2025-09-06 22:14:43 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-06 22:14:43 (10381) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 22:14:44 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-06 22:14:44 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-06 22:14:44 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-06 22:14:44 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-06 22:14:44 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-06 22:14:44 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-06 22:14:44 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-06 22:14:44 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-06 22:14:44 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-06 22:14:44 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-06 22:14:44 (10394) [INFO] yum --disablerepo= ... * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-06 22:14:44 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-06 22:14:44 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] yum-config-manager --disable * 2025-09-06 22:14:44 (10394) [INFO] or * 2025-09-06 22:14:44 (10394) [INFO] subscription-manager repos --disable= * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-06 22:14:44 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-06 22:14:44 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-06 22:14:44 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-06 22:14:44 (10394) [INFO] compromise: * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-06 22:14:44 (10394) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-06 22:14:44 (10394) [INFO] * free 0 * 2025-09-06 22:14:44 (10394) [INFO] * needed 100 k * 2025-09-06 22:14:44 (10411) [INFO] * 2025-09-06 22:14:44 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-06 22:14:44 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-06 22:14:44 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-06 22:14:44 (10381) [INFO] * 2025-09-06 22:14:44 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 22:14:45 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-06 22:14:45 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-06 22:14:45 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-06 22:14:45 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-06 22:14:45 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-06 22:14:45 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-06 22:14:45 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-06 22:14:45 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-06 22:14:45 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-06 22:14:45 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-06 22:14:45 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-06 22:14:45 (10411) [INFO] * 2025-09-06 22:14:45 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-06 22:14:45 (10381) [INFO] * 2025-09-06 22:14:45 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-06 22:14:45 (10394) [INFO] Determining fastest mirrors * 2025-09-06 22:14:46 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-06 22:14:46 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-06 22:14:46 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-06 22:14:46 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-06 22:14:46 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-06 22:14:46 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-06 22:14:46 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-06 22:14:46 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-06 22:14:46 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-06 22:14:46 (10394) [INFO] yum --disablerepo= ... * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-06 22:14:46 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-06 22:14:46 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] yum-config-manager --disable * 2025-09-06 22:14:46 (10394) [INFO] or * 2025-09-06 22:14:46 (10394) [INFO] subscription-manager repos --disable= * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-06 22:14:46 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-06 22:14:46 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-06 22:14:46 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-06 22:14:46 (10394) [INFO] compromise: * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-06 22:14:46 (10394) [INFO] * 2025-09-06 22:14:46 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-06 22:14:46 (10394) [INFO] * free 0 * 2025-09-06 22:14:46 (10394) [INFO] * needed 100 k * 2025-09-06 22:14:46 (10411) [INFO] * 2025-09-06 22:14:46 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-06 22:14:46 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-06 22:14:46 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-06 22:14:46 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cwOSwMG94D/ea_profile.json * 2025-09-06 22:14:47 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cwOSwMG94D/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-06 22:14:47 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-07 22:14:02 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-07 22:14:02 (11467) [INFO] Script is up to date. * 2025-09-07 22:14:03 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-07 22:14:03 (10381) [INFO] * 2025-09-07 22:14:31 (10411) [INFO] * 2025-09-07 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-07 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-07 22:14:31 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-07 22:14:31 (10381) [INFO] * 2025-09-07 22:14:34 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-07 22:14:34 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-07 22:14:34 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-07 22:14:34 (10381) [INFO] * 2025-09-07 22:14:36 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-07 22:14:36 (10381) [INFO] * 2025-09-07 22:14:36 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 22:14:36 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-07 22:14:37 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-07 22:14:37 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-07 22:14:37 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-07 22:14:37 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-07 22:14:37 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-07 22:14:37 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-07 22:14:37 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-07 22:14:37 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-07 22:14:37 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-07 22:14:37 (10394) [INFO] yum --disablerepo= ... * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-07 22:14:37 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-07 22:14:37 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] yum-config-manager --disable * 2025-09-07 22:14:37 (10394) [INFO] or * 2025-09-07 22:14:37 (10394) [INFO] subscription-manager repos --disable= * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-07 22:14:37 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-07 22:14:37 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-07 22:14:37 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-07 22:14:37 (10394) [INFO] compromise: * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-07 22:14:37 (10394) [INFO] * 2025-09-07 22:14:37 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-07 22:14:37 (10394) [INFO] * free 0 * 2025-09-07 22:14:37 (10394) [INFO] * needed 100 k * 2025-09-07 22:14:37 (10411) [INFO] * 2025-09-07 22:14:37 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-07 22:14:37 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-07 22:14:37 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-07 22:14:37 (10381) [INFO] * 2025-09-07 22:14:38 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 22:14:38 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-07 22:14:38 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-07 22:14:38 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-07 22:14:38 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-07 22:14:38 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-07 22:14:38 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-07 22:14:38 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-07 22:14:38 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-07 22:14:38 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-07 22:14:38 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-07 22:14:38 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-07 22:14:38 (10411) [INFO] * 2025-09-07 22:14:38 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-07 22:14:38 (10381) [INFO] * 2025-09-07 22:14:38 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-07 22:14:38 (10394) [INFO] Determining fastest mirrors * 2025-09-07 22:14:40 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-07 22:14:40 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-07 22:14:40 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-07 22:14:40 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-07 22:14:40 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-07 22:14:40 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-07 22:14:40 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-07 22:14:40 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-07 22:14:40 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-07 22:14:40 (10394) [INFO] yum --disablerepo= ... * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-07 22:14:40 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-07 22:14:40 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] yum-config-manager --disable * 2025-09-07 22:14:40 (10394) [INFO] or * 2025-09-07 22:14:40 (10394) [INFO] subscription-manager repos --disable= * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-07 22:14:40 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-07 22:14:40 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-07 22:14:40 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-07 22:14:40 (10394) [INFO] compromise: * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-07 22:14:40 (10394) [INFO] * 2025-09-07 22:14:40 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-07 22:14:40 (10394) [INFO] * free 0 * 2025-09-07 22:14:40 (10394) [INFO] * needed 100 k * 2025-09-07 22:14:40 (10411) [INFO] * 2025-09-07 22:14:40 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-07 22:14:40 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-07 22:14:41 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-07 22:14:42 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DAY3nRzMAr/ea_profile.json * 2025-09-07 22:14:42 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DAY3nRzMAr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-07 22:14:42 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-08 22:13:33 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-08 22:13:33 (11467) [INFO] Script is up to date. * 2025-09-08 22:13:35 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-08 22:13:35 (10381) [INFO] * 2025-09-08 22:14:03 (10411) [INFO] * 2025-09-08 22:14:03 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-08 22:14:03 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.71. * 2025-09-08 22:14:03 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-08 22:14:03 (10381) [INFO] * 2025-09-08 22:14:06 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-08 22:14:06 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-08 22:14:06 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-08 22:14:06 (10381) [INFO] * 2025-09-08 22:14:09 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-08 22:14:09 (10381) [INFO] * 2025-09-08 22:14:09 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 22:14:09 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-08 22:14:10 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-08 22:14:10 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-08 22:14:10 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-08 22:14:10 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-08 22:14:10 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-08 22:14:10 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-08 22:14:10 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-08 22:14:10 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-08 22:14:10 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-08 22:14:10 (10394) [INFO] yum --disablerepo= ... * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-08 22:14:10 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-08 22:14:10 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] yum-config-manager --disable * 2025-09-08 22:14:10 (10394) [INFO] or * 2025-09-08 22:14:10 (10394) [INFO] subscription-manager repos --disable= * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-08 22:14:10 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-08 22:14:10 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-08 22:14:10 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-08 22:14:10 (10394) [INFO] compromise: * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-08 22:14:10 (10394) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-08 22:14:10 (10394) [INFO] * free 0 * 2025-09-08 22:14:10 (10394) [INFO] * needed 100 k * 2025-09-08 22:14:10 (10411) [INFO] * 2025-09-08 22:14:10 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-08 22:14:10 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-08 22:14:10 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-08 22:14:10 (10381) [INFO] * 2025-09-08 22:14:10 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 22:14:11 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-08 22:14:11 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-08 22:14:11 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-08 22:14:11 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-08 22:14:11 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-08 22:14:11 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-08 22:14:11 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-08 22:14:11 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-08 22:14:11 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-08 22:14:11 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-08 22:14:11 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-08 22:14:11 (10411) [INFO] * 2025-09-08 22:14:11 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-08 22:14:11 (10381) [INFO] * 2025-09-08 22:14:11 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-08 22:14:11 (10394) [INFO] Determining fastest mirrors * 2025-09-08 22:14:14 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-08 22:14:14 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-08 22:14:14 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-08 22:14:14 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-08 22:14:14 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-08 22:14:14 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-08 22:14:14 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-08 22:14:14 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-08 22:14:14 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-08 22:14:14 (10394) [INFO] yum --disablerepo= ... * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-08 22:14:14 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-08 22:14:14 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] yum-config-manager --disable * 2025-09-08 22:14:14 (10394) [INFO] or * 2025-09-08 22:14:14 (10394) [INFO] subscription-manager repos --disable= * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-08 22:14:14 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-08 22:14:14 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-08 22:14:14 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-08 22:14:14 (10394) [INFO] compromise: * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-08 22:14:14 (10394) [INFO] * 2025-09-08 22:14:14 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-08 22:14:14 (10394) [INFO] * free 0 * 2025-09-08 22:14:14 (10394) [INFO] * needed 100 k * 2025-09-08 22:14:14 (10411) [INFO] * 2025-09-08 22:14:14 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-08 22:14:14 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-08 22:14:14 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-08 22:14:15 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QwnFcOboZf/ea_profile.json * 2025-09-08 22:14:15 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QwnFcOboZf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-08 22:14:15 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-09 22:13:34 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-09 22:13:34 (11467) [INFO] Script is up to date. * 2025-09-09 22:13:35 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-09 22:13:35 (10381) [INFO] * 2025-09-09 22:14:04 (10411) [INFO] * 2025-09-09 22:14:04 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-09 22:14:04 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.73. * 2025-09-09 22:14:04 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-09 22:14:04 (10381) [INFO] * 2025-09-09 22:14:07 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-09 22:14:07 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-09 22:14:07 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-09 22:14:07 (10381) [INFO] * 2025-09-09 22:14:10 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-09 22:14:10 (10381) [INFO] * 2025-09-09 22:14:10 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 22:14:10 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-09 22:14:11 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-09 22:14:11 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-09 22:14:11 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-09 22:14:11 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-09 22:14:11 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-09 22:14:11 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-09 22:14:11 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-09 22:14:11 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-09 22:14:11 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-09 22:14:11 (10394) [INFO] yum --disablerepo= ... * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-09 22:14:11 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-09 22:14:11 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] yum-config-manager --disable * 2025-09-09 22:14:11 (10394) [INFO] or * 2025-09-09 22:14:11 (10394) [INFO] subscription-manager repos --disable= * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-09 22:14:11 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-09 22:14:11 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-09 22:14:11 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-09 22:14:11 (10394) [INFO] compromise: * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-09 22:14:11 (10394) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-09 22:14:11 (10394) [INFO] * free 0 * 2025-09-09 22:14:11 (10394) [INFO] * needed 100 k * 2025-09-09 22:14:11 (10411) [INFO] * 2025-09-09 22:14:11 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-09 22:14:11 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-09 22:14:11 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-09 22:14:11 (10381) [INFO] * 2025-09-09 22:14:11 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 22:14:11 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-09 22:14:11 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-09 22:14:11 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-09 22:14:11 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-09 22:14:11 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-09 22:14:11 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-09 22:14:11 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-09 22:14:11 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-09 22:14:11 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-09 22:14:11 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-09 22:14:11 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-09 22:14:11 (10411) [INFO] * 2025-09-09 22:14:11 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-09 22:14:11 (10381) [INFO] * 2025-09-09 22:14:12 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-09 22:14:12 (10394) [INFO] Determining fastest mirrors * 2025-09-09 22:14:13 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-09 22:14:13 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-09 22:14:13 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-09 22:14:13 (10394) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-09 22:14:13 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-09 22:14:13 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-09 22:14:13 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-09 22:14:13 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-09 22:14:13 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-09 22:14:13 (10394) [INFO] yum --disablerepo= ... * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-09 22:14:13 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-09 22:14:13 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] yum-config-manager --disable * 2025-09-09 22:14:13 (10394) [INFO] or * 2025-09-09 22:14:13 (10394) [INFO] subscription-manager repos --disable= * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-09 22:14:13 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-09 22:14:13 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-09 22:14:13 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-09 22:14:13 (10394) [INFO] compromise: * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-09 22:14:13 (10394) [INFO] * 2025-09-09 22:14:13 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-09 22:14:13 (10394) [INFO] * free 0 * 2025-09-09 22:14:13 (10394) [INFO] * needed 100 k * 2025-09-09 22:14:13 (10411) [INFO] * 2025-09-09 22:14:13 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-09 22:14:13 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-09 22:14:14 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-09 22:14:14 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wLqJTBMn60/ea_profile.json * 2025-09-09 22:14:15 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wLqJTBMn60/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-09 22:14:15 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-10 22:13:36 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-10 22:13:36 (11467) [INFO] Script is up to date. * 2025-09-10 22:13:37 (10380) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-10 22:13:37 (10381) [INFO] * 2025-09-10 22:14:14 (10411) [INFO] * 2025-09-10 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-10 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.73. * 2025-09-10 22:14:14 (10380) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-10 22:14:14 (10381) [INFO] * 2025-09-10 22:14:16 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-10 22:14:16 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-10 22:14:16 (10380) [INFO] Running: /usr/bin/yum list extras * 2025-09-10 22:14:16 (10381) [INFO] * 2025-09-10 22:14:20 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-10 22:14:20 (10381) [INFO] * 2025-09-10 22:14:20 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 22:14:20 (10394) [INFO] Loading mirror speeds from cached hostfile * 2025-09-10 22:14:21 (10394) [INFO] * EA4: 89.222.122.161 * 2025-09-10 22:14:21 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-10 22:14:21 (10394) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-10 22:14:21 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-10 22:14:21 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-10 22:14:21 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-10 22:14:21 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-10 22:14:21 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-10 22:14:21 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-10 22:14:21 (10394) [INFO] yum --disablerepo= ... * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-10 22:14:21 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-10 22:14:21 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] yum-config-manager --disable * 2025-09-10 22:14:21 (10394) [INFO] or * 2025-09-10 22:14:21 (10394) [INFO] subscription-manager repos --disable= * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-10 22:14:21 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-10 22:14:21 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-10 22:14:21 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-10 22:14:21 (10394) [INFO] compromise: * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-10 22:14:21 (10394) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-10 22:14:21 (10394) [INFO] * free 0 * 2025-09-10 22:14:21 (10394) [INFO] * needed 100 k * 2025-09-10 22:14:21 (10411) [INFO] * 2025-09-10 22:14:21 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-10 22:14:21 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-10 22:14:21 (10380) [INFO] Running: /usr/bin/yum clean all * 2025-09-10 22:14:21 (10381) [INFO] * 2025-09-10 22:14:21 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 22:14:21 (10394) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-10 22:14:21 (10394) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-10 22:14:21 (10394) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-10 22:14:21 (10394) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-10 22:14:21 (10394) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-10 22:14:21 (10394) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-10 22:14:21 (10394) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-10 22:14:21 (10394) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-10 22:14:21 (10394) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-10 22:14:22 (10394) [INFO] Cleaning up list of fastest mirrors * 2025-09-10 22:14:22 (10394) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-10 22:14:22 (10411) [INFO] * 2025-09-10 22:14:22 (10380) [INFO] Running: /usr/bin/yum makecache * 2025-09-10 22:14:22 (10381) [INFO] * 2025-09-10 22:14:22 (10394) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-10 22:14:22 (10394) [INFO] Determining fastest mirrors * 2025-09-10 22:14:23 (10394) [INFO] * EA4: 89.222.122.163 * 2025-09-10 22:14:23 (10394) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-10 22:14:23 (10394) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-10 22:14:23 (10394) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] One of the configured repositories failed (Unknown), * 2025-09-10 22:14:23 (10394) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-10 22:14:23 (10394) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-10 22:14:23 (10394) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-10 22:14:23 (10394) [INFO] distribution release than is supported by the repository (and the * 2025-09-10 22:14:23 (10394) [INFO] packages for the previous distribution release still work). * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-10 22:14:23 (10394) [INFO] yum --disablerepo= ... * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-10 22:14:23 (10394) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-10 22:14:23 (10394) [INFO] again or use --enablerepo for temporary usage: * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] yum-config-manager --disable * 2025-09-10 22:14:23 (10394) [INFO] or * 2025-09-10 22:14:23 (10394) [INFO] subscription-manager repos --disable= * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-10 22:14:23 (10394) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-10 22:14:23 (10394) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-10 22:14:23 (10394) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-10 22:14:23 (10394) [INFO] compromise: * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-10 22:14:23 (10394) [INFO] * 2025-09-10 22:14:23 (10394) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-10 22:14:23 (10394) [INFO] * free 0 * 2025-09-10 22:14:23 (10394) [INFO] * needed 100 k * 2025-09-10 22:14:23 (10411) [INFO] * 2025-09-10 22:14:23 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-10 22:14:23 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-10 22:14:24 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-10 22:14:24 (9454) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VDJibXJwn5/ea_profile.json * 2025-09-10 22:14:25 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VDJibXJwn5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9456. * 2025-09-10 22:14:25 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-11 22:13:34 (11445) [INFO] Self-update of script version 70 requested. * 2025-09-11 22:13:34 (11450) [INFO] Newer version of script found. Downloading. * 2025-09-11 22:13:34 (11459) [INFO] Script update to version 71 successful. * 2025-09-11 22:13:35 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-11 22:13:35 (10379) [INFO] * 2025-09-11 22:14:09 (10409) [INFO] * 2025-09-11 22:14:09 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-11 22:14:09 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-11 22:14:09 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-11 22:14:09 (10379) [INFO] * 2025-09-11 22:14:12 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-11 22:14:12 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-11 22:14:12 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-11 22:14:12 (10379) [INFO] * 2025-09-11 22:14:14 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-11 22:14:14 (10379) [INFO] * 2025-09-11 22:14:14 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 22:14:14 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-11 22:14:15 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-11 22:14:15 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-11 22:14:15 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-11 22:14:15 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-11 22:14:15 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-11 22:14:15 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-11 22:14:15 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-11 22:14:15 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-11 22:14:15 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-11 22:14:15 (10392) [INFO] yum --disablerepo= ... * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-11 22:14:15 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-11 22:14:15 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] yum-config-manager --disable * 2025-09-11 22:14:15 (10392) [INFO] or * 2025-09-11 22:14:15 (10392) [INFO] subscription-manager repos --disable= * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-11 22:14:15 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-11 22:14:15 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-11 22:14:15 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-11 22:14:15 (10392) [INFO] compromise: * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-11 22:14:15 (10392) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-11 22:14:15 (10392) [INFO] * free 0 * 2025-09-11 22:14:15 (10392) [INFO] * needed 100 k * 2025-09-11 22:14:15 (10409) [INFO] * 2025-09-11 22:14:15 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-11 22:14:15 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-11 22:14:15 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-11 22:14:15 (10379) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 22:14:15 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-11 22:14:15 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-11 22:14:15 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-11 22:14:15 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-11 22:14:15 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-11 22:14:15 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-11 22:14:15 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-11 22:14:15 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-11 22:14:15 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-11 22:14:15 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-11 22:14:15 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-11 22:14:15 (10409) [INFO] * 2025-09-11 22:14:15 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-11 22:14:15 (10379) [INFO] * 2025-09-11 22:14:15 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-11 22:14:15 (10392) [INFO] Determining fastest mirrors * 2025-09-11 22:14:16 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-11 22:14:16 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-11 22:14:16 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-11 22:14:16 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-11 22:14:16 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-11 22:14:16 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-11 22:14:16 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-11 22:14:16 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-11 22:14:16 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-11 22:14:16 (10392) [INFO] yum --disablerepo= ... * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-11 22:14:16 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-11 22:14:16 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] yum-config-manager --disable * 2025-09-11 22:14:16 (10392) [INFO] or * 2025-09-11 22:14:16 (10392) [INFO] subscription-manager repos --disable= * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-11 22:14:16 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-11 22:14:16 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-11 22:14:16 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-11 22:14:16 (10392) [INFO] compromise: * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-11 22:14:16 (10392) [INFO] * 2025-09-11 22:14:16 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-11 22:14:16 (10392) [INFO] * free 0 * 2025-09-11 22:14:16 (10392) [INFO] * needed 100 k * 2025-09-11 22:14:16 (10409) [INFO] * 2025-09-11 22:14:16 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-11 22:14:16 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-11 22:14:17 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-11 22:14:17 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7GSvPJUqTi/ea_profile.json * 2025-09-11 22:14:18 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7GSvPJUqTi/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-11 22:14:18 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-12 22:13:34 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-12 22:13:34 (11465) [INFO] Script is up to date. * 2025-09-12 22:13:35 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-12 22:13:35 (10379) [INFO] * 2025-09-12 22:14:18 (10409) [INFO] * 2025-09-12 22:14:18 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-12 22:14:18 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-12 22:14:18 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-12 22:14:18 (10379) [INFO] * 2025-09-12 22:14:21 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-12 22:14:21 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-12 22:14:21 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-12 22:14:21 (10379) [INFO] * 2025-09-12 22:14:23 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-12 22:14:23 (10379) [INFO] * 2025-09-12 22:14:23 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 22:14:23 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-12 22:14:24 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-12 22:14:24 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-12 22:14:24 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-12 22:14:24 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-12 22:14:24 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-12 22:14:24 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-12 22:14:24 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-12 22:14:24 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-12 22:14:24 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-12 22:14:24 (10392) [INFO] yum --disablerepo= ... * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-12 22:14:24 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-12 22:14:24 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] yum-config-manager --disable * 2025-09-12 22:14:24 (10392) [INFO] or * 2025-09-12 22:14:24 (10392) [INFO] subscription-manager repos --disable= * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-12 22:14:24 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-12 22:14:24 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-12 22:14:24 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-12 22:14:24 (10392) [INFO] compromise: * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-12 22:14:24 (10392) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-12 22:14:24 (10392) [INFO] * free 0 * 2025-09-12 22:14:24 (10392) [INFO] * needed 100 k * 2025-09-12 22:14:24 (10409) [INFO] * 2025-09-12 22:14:24 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-12 22:14:24 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-12 22:14:24 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-12 22:14:24 (10379) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 22:14:24 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-12 22:14:24 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-12 22:14:24 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-12 22:14:24 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-12 22:14:24 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-12 22:14:24 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-12 22:14:24 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-12 22:14:24 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-12 22:14:24 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-12 22:14:24 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-12 22:14:24 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-12 22:14:24 (10409) [INFO] * 2025-09-12 22:14:24 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-12 22:14:24 (10379) [INFO] * 2025-09-12 22:14:24 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-12 22:14:24 (10392) [INFO] Determining fastest mirrors * 2025-09-12 22:14:25 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-12 22:14:25 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-12 22:14:25 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-12 22:14:25 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-12 22:14:25 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-12 22:14:25 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-12 22:14:25 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-12 22:14:25 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-12 22:14:25 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-12 22:14:25 (10392) [INFO] yum --disablerepo= ... * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-12 22:14:25 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-12 22:14:25 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] yum-config-manager --disable * 2025-09-12 22:14:25 (10392) [INFO] or * 2025-09-12 22:14:25 (10392) [INFO] subscription-manager repos --disable= * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-12 22:14:25 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-12 22:14:25 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-12 22:14:25 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-12 22:14:25 (10392) [INFO] compromise: * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-12 22:14:25 (10392) [INFO] * 2025-09-12 22:14:25 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-12 22:14:25 (10392) [INFO] * free 0 * 2025-09-12 22:14:25 (10392) [INFO] * needed 100 k * 2025-09-12 22:14:25 (10409) [INFO] * 2025-09-12 22:14:25 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-12 22:14:25 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-12 22:14:26 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-12 22:14:26 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZsbKSy2dn8/ea_profile.json * 2025-09-12 22:14:27 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ZsbKSy2dn8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-12 22:14:27 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-13 22:14:33 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-13 22:14:33 (11465) [INFO] Script is up to date. * 2025-09-13 22:14:34 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-13 22:14:34 (10379) [INFO] * 2025-09-13 22:15:06 (10409) [INFO] * 2025-09-13 22:15:06 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-13 22:15:06 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-13 22:15:06 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-13 22:15:06 (10379) [INFO] * 2025-09-13 22:15:09 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-13 22:15:09 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-13 22:15:09 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-13 22:15:09 (10379) [INFO] * 2025-09-13 22:15:12 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-13 22:15:12 (10379) [INFO] * 2025-09-13 22:15:12 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 22:15:12 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-13 22:15:13 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-13 22:15:13 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-13 22:15:13 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-13 22:15:13 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-13 22:15:13 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-13 22:15:13 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-13 22:15:13 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-13 22:15:13 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-13 22:15:13 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-13 22:15:13 (10392) [INFO] yum --disablerepo= ... * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-13 22:15:13 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-13 22:15:13 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] yum-config-manager --disable * 2025-09-13 22:15:13 (10392) [INFO] or * 2025-09-13 22:15:13 (10392) [INFO] subscription-manager repos --disable= * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-13 22:15:13 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-13 22:15:13 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-13 22:15:13 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-13 22:15:13 (10392) [INFO] compromise: * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-13 22:15:13 (10392) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-13 22:15:13 (10392) [INFO] * free 0 * 2025-09-13 22:15:13 (10392) [INFO] * needed 100 k * 2025-09-13 22:15:13 (10409) [INFO] * 2025-09-13 22:15:13 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-13 22:15:13 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-13 22:15:13 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-13 22:15:13 (10379) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 22:15:13 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-13 22:15:13 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-13 22:15:13 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-13 22:15:13 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-13 22:15:13 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-13 22:15:13 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-13 22:15:13 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-13 22:15:13 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-13 22:15:13 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-13 22:15:13 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-13 22:15:13 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-13 22:15:13 (10409) [INFO] * 2025-09-13 22:15:13 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-13 22:15:13 (10379) [INFO] * 2025-09-13 22:15:13 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-13 22:15:14 (10392) [INFO] Determining fastest mirrors * 2025-09-13 22:15:17 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-13 22:15:17 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-13 22:15:17 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-13 22:15:17 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-13 22:15:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-13 22:15:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-13 22:15:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-13 22:15:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-13 22:15:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-13 22:15:17 (10392) [INFO] yum --disablerepo= ... * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-13 22:15:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-13 22:15:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] yum-config-manager --disable * 2025-09-13 22:15:17 (10392) [INFO] or * 2025-09-13 22:15:17 (10392) [INFO] subscription-manager repos --disable= * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-13 22:15:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-13 22:15:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-13 22:15:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-13 22:15:17 (10392) [INFO] compromise: * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-13 22:15:17 (10392) [INFO] * 2025-09-13 22:15:17 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-13 22:15:17 (10392) [INFO] * free 0 * 2025-09-13 22:15:17 (10392) [INFO] * needed 100 k * 2025-09-13 22:15:17 (10409) [INFO] * 2025-09-13 22:15:17 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-13 22:15:17 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-13 22:15:17 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-13 22:15:18 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sm8p7ZampZ/ea_profile.json * 2025-09-13 22:15:19 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sm8p7ZampZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-13 22:15:19 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-14 22:14:10 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-14 22:14:10 (11465) [INFO] Script is up to date. * 2025-09-14 22:14:11 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-14 22:14:11 (10379) [INFO] * 2025-09-14 22:14:44 (10409) [INFO] * 2025-09-14 22:14:44 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-14 22:14:44 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-14 22:14:44 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-14 22:14:44 (10379) [INFO] * 2025-09-14 22:14:47 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-14 22:14:47 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-14 22:14:47 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-14 22:14:47 (10379) [INFO] * 2025-09-14 22:14:50 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-14 22:14:50 (10379) [INFO] * 2025-09-14 22:14:50 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 22:14:51 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-14 22:14:51 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-14 22:14:51 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-14 22:14:51 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-14 22:14:51 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-14 22:14:51 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-14 22:14:51 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-14 22:14:51 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-14 22:14:51 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-14 22:14:51 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-14 22:14:51 (10392) [INFO] yum --disablerepo= ... * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-14 22:14:51 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-14 22:14:51 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] yum-config-manager --disable * 2025-09-14 22:14:51 (10392) [INFO] or * 2025-09-14 22:14:51 (10392) [INFO] subscription-manager repos --disable= * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-14 22:14:51 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-14 22:14:51 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-14 22:14:51 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-14 22:14:51 (10392) [INFO] compromise: * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-14 22:14:51 (10392) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-14 22:14:51 (10392) [INFO] * free 0 * 2025-09-14 22:14:51 (10392) [INFO] * needed 100 k * 2025-09-14 22:14:51 (10409) [INFO] * 2025-09-14 22:14:51 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-14 22:14:51 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-14 22:14:51 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-14 22:14:51 (10379) [INFO] * 2025-09-14 22:14:51 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 22:14:52 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-14 22:14:52 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-14 22:14:52 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-14 22:14:52 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-14 22:14:52 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-14 22:14:52 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-14 22:14:52 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-14 22:14:52 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-14 22:14:52 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-14 22:14:52 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-14 22:14:52 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-14 22:14:52 (10409) [INFO] * 2025-09-14 22:14:52 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-14 22:14:52 (10379) [INFO] * 2025-09-14 22:14:52 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-14 22:14:52 (10392) [INFO] Determining fastest mirrors * 2025-09-14 22:14:53 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-14 22:14:53 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-14 22:14:53 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-14 22:14:53 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-14 22:14:53 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-14 22:14:53 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-14 22:14:53 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-14 22:14:53 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-14 22:14:53 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-14 22:14:53 (10392) [INFO] yum --disablerepo= ... * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-14 22:14:53 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-14 22:14:53 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] yum-config-manager --disable * 2025-09-14 22:14:53 (10392) [INFO] or * 2025-09-14 22:14:53 (10392) [INFO] subscription-manager repos --disable= * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-14 22:14:53 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-14 22:14:53 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-14 22:14:53 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-14 22:14:53 (10392) [INFO] compromise: * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-14 22:14:53 (10392) [INFO] * 2025-09-14 22:14:53 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-14 22:14:53 (10392) [INFO] * free 0 * 2025-09-14 22:14:53 (10392) [INFO] * needed 100 k * 2025-09-14 22:14:53 (10409) [INFO] * 2025-09-14 22:14:53 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-14 22:14:53 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-14 22:14:54 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-14 22:14:54 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vSHlt_jWpC/ea_profile.json * 2025-09-14 22:14:55 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vSHlt_jWpC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-14 22:14:55 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-15 22:13:33 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-15 22:13:33 (11465) [INFO] Script is up to date. * 2025-09-15 22:13:35 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-15 22:13:35 (10379) [INFO] * 2025-09-15 22:14:09 (10409) [INFO] * 2025-09-15 22:14:09 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-15 22:14:09 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-15 22:14:09 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-15 22:14:09 (10379) [INFO] * 2025-09-15 22:14:12 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-15 22:14:12 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-15 22:14:12 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-15 22:14:12 (10379) [INFO] * 2025-09-15 22:14:15 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-15 22:14:15 (10379) [INFO] * 2025-09-15 22:14:15 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 22:14:15 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-15 22:14:17 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-15 22:14:17 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-15 22:14:17 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-15 22:14:17 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-15 22:14:17 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-15 22:14:17 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-15 22:14:17 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-15 22:14:17 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-15 22:14:17 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-15 22:14:17 (10392) [INFO] yum --disablerepo= ... * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-15 22:14:17 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-15 22:14:17 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] yum-config-manager --disable * 2025-09-15 22:14:17 (10392) [INFO] or * 2025-09-15 22:14:17 (10392) [INFO] subscription-manager repos --disable= * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-15 22:14:17 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-15 22:14:17 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-15 22:14:17 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-15 22:14:17 (10392) [INFO] compromise: * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-15 22:14:17 (10392) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-15 22:14:17 (10392) [INFO] * free 0 * 2025-09-15 22:14:17 (10392) [INFO] * needed 100 k * 2025-09-15 22:14:17 (10409) [INFO] * 2025-09-15 22:14:17 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-15 22:14:17 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-15 22:14:17 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-15 22:14:17 (10379) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 22:14:17 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-15 22:14:17 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-15 22:14:17 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-15 22:14:17 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-15 22:14:17 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-15 22:14:17 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-15 22:14:17 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-15 22:14:17 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-15 22:14:17 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-15 22:14:17 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-15 22:14:17 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-15 22:14:17 (10409) [INFO] * 2025-09-15 22:14:17 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-15 22:14:17 (10379) [INFO] * 2025-09-15 22:14:17 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-15 22:14:17 (10392) [INFO] Determining fastest mirrors * 2025-09-15 22:14:19 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-15 22:14:19 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-15 22:14:19 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-15 22:14:19 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-15 22:14:19 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-15 22:14:19 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-15 22:14:19 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-15 22:14:19 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-15 22:14:19 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-15 22:14:19 (10392) [INFO] yum --disablerepo= ... * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-15 22:14:19 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-15 22:14:19 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] yum-config-manager --disable * 2025-09-15 22:14:19 (10392) [INFO] or * 2025-09-15 22:14:19 (10392) [INFO] subscription-manager repos --disable= * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-15 22:14:19 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-15 22:14:19 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-15 22:14:19 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-15 22:14:19 (10392) [INFO] compromise: * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-15 22:14:19 (10392) [INFO] * 2025-09-15 22:14:19 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-15 22:14:19 (10392) [INFO] * free 0 * 2025-09-15 22:14:19 (10392) [INFO] * needed 100 k * 2025-09-15 22:14:19 (10409) [INFO] * 2025-09-15 22:14:19 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-15 22:14:19 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-15 22:14:19 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-15 22:14:20 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qUtn6Btax4/ea_profile.json * 2025-09-15 22:14:20 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qUtn6Btax4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-15 22:14:20 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-16 22:13:41 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-16 22:13:41 (11465) [INFO] Script is up to date. * 2025-09-16 22:13:42 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-16 22:13:42 (10379) [INFO] * 2025-09-16 22:14:28 (10409) [INFO] * 2025-09-16 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-16 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-16 22:14:28 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-16 22:14:28 (10379) [INFO] * 2025-09-16 22:14:31 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-16 22:14:31 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-16 22:14:31 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-16 22:14:31 (10379) [INFO] * 2025-09-16 22:14:34 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-16 22:14:34 (10379) [INFO] * 2025-09-16 22:14:34 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 22:14:34 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-16 22:14:35 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-16 22:14:35 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-16 22:14:35 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-16 22:14:35 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-16 22:14:35 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-16 22:14:35 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-16 22:14:35 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-16 22:14:35 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-16 22:14:35 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-16 22:14:35 (10392) [INFO] yum --disablerepo= ... * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-16 22:14:35 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-16 22:14:35 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] yum-config-manager --disable * 2025-09-16 22:14:35 (10392) [INFO] or * 2025-09-16 22:14:35 (10392) [INFO] subscription-manager repos --disable= * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-16 22:14:35 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-16 22:14:35 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-16 22:14:35 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-16 22:14:35 (10392) [INFO] compromise: * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-16 22:14:35 (10392) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-16 22:14:35 (10392) [INFO] * free 0 * 2025-09-16 22:14:35 (10392) [INFO] * needed 100 k * 2025-09-16 22:14:35 (10409) [INFO] * 2025-09-16 22:14:35 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-16 22:14:35 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-16 22:14:35 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-16 22:14:35 (10379) [INFO] * 2025-09-16 22:14:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 22:14:35 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-16 22:14:35 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-16 22:14:35 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-16 22:14:35 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-16 22:14:35 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-16 22:14:35 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-16 22:14:35 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-16 22:14:35 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-16 22:14:35 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-16 22:14:35 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-16 22:14:35 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-16 22:14:36 (10409) [INFO] * 2025-09-16 22:14:36 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-16 22:14:36 (10379) [INFO] * 2025-09-16 22:14:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-16 22:14:36 (10392) [INFO] Determining fastest mirrors * 2025-09-16 22:14:37 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-16 22:14:37 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-16 22:14:37 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-16 22:14:37 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-16 22:14:37 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-16 22:14:37 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-16 22:14:37 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-16 22:14:37 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-16 22:14:37 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-16 22:14:37 (10392) [INFO] yum --disablerepo= ... * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-16 22:14:37 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-16 22:14:37 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] yum-config-manager --disable * 2025-09-16 22:14:37 (10392) [INFO] or * 2025-09-16 22:14:37 (10392) [INFO] subscription-manager repos --disable= * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-16 22:14:37 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-16 22:14:37 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-16 22:14:37 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-16 22:14:37 (10392) [INFO] compromise: * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-16 22:14:37 (10392) [INFO] * 2025-09-16 22:14:37 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-16 22:14:37 (10392) [INFO] * free 0 * 2025-09-16 22:14:37 (10392) [INFO] * needed 100 k * 2025-09-16 22:14:37 (10409) [INFO] * 2025-09-16 22:14:37 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-16 22:14:37 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-16 22:14:38 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-16 22:14:38 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u3pcmkNK7a/ea_profile.json * 2025-09-16 22:14:39 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u3pcmkNK7a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-16 22:14:39 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-17 22:13:51 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-17 22:13:51 (11465) [INFO] Script is up to date. * 2025-09-17 22:13:53 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-17 22:13:53 (10379) [INFO] * 2025-09-17 22:14:46 (10409) [INFO] * 2025-09-17 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-17 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.74. * 2025-09-17 22:14:46 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-17 22:14:46 (10379) [INFO] * 2025-09-17 22:14:51 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-17 22:14:51 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-17 22:14:51 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-17 22:14:51 (10379) [INFO] * 2025-09-17 22:14:54 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-17 22:14:54 (10379) [INFO] * 2025-09-17 22:14:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 22:14:54 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-17 22:14:55 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-17 22:14:55 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-17 22:14:55 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-17 22:14:55 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-17 22:14:55 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-17 22:14:55 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-17 22:14:55 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-17 22:14:55 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-17 22:14:55 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-17 22:14:55 (10392) [INFO] yum --disablerepo= ... * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-17 22:14:55 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-17 22:14:55 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] yum-config-manager --disable * 2025-09-17 22:14:55 (10392) [INFO] or * 2025-09-17 22:14:55 (10392) [INFO] subscription-manager repos --disable= * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-17 22:14:55 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-17 22:14:55 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-17 22:14:55 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-17 22:14:55 (10392) [INFO] compromise: * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-17 22:14:55 (10392) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-17 22:14:55 (10392) [INFO] * free 0 * 2025-09-17 22:14:55 (10392) [INFO] * needed 100 k * 2025-09-17 22:14:55 (10409) [INFO] * 2025-09-17 22:14:55 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-17 22:14:55 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-17 22:14:55 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-17 22:14:55 (10379) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 22:14:55 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-17 22:14:55 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-17 22:14:55 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-17 22:14:55 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-17 22:14:55 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-17 22:14:55 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-17 22:14:55 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-17 22:14:55 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-17 22:14:55 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-17 22:14:55 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-17 22:14:55 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-17 22:14:55 (10409) [INFO] * 2025-09-17 22:14:55 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-17 22:14:55 (10379) [INFO] * 2025-09-17 22:14:55 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-17 22:14:55 (10392) [INFO] Determining fastest mirrors * 2025-09-17 22:14:56 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-17 22:14:56 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-17 22:14:56 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-17 22:14:56 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-17 22:14:56 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-17 22:14:56 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-17 22:14:56 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-17 22:14:56 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-17 22:14:56 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-17 22:14:56 (10392) [INFO] yum --disablerepo= ... * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-17 22:14:56 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-17 22:14:56 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] yum-config-manager --disable * 2025-09-17 22:14:56 (10392) [INFO] or * 2025-09-17 22:14:56 (10392) [INFO] subscription-manager repos --disable= * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-17 22:14:56 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-17 22:14:56 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-17 22:14:56 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-17 22:14:56 (10392) [INFO] compromise: * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-17 22:14:56 (10392) [INFO] * 2025-09-17 22:14:56 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-17 22:14:56 (10392) [INFO] * free 0 * 2025-09-17 22:14:56 (10392) [INFO] * needed 100 k * 2025-09-17 22:14:56 (10409) [INFO] * 2025-09-17 22:14:56 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-17 22:14:56 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-17 22:14:57 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-17 22:14:57 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FgFhP0kYjH/ea_profile.json * 2025-09-17 22:14:58 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FgFhP0kYjH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-17 22:14:58 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-18 22:13:41 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-18 22:13:42 (11465) [INFO] Script is up to date. * 2025-09-18 22:13:43 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-18 22:13:43 (10379) [INFO] * 2025-09-18 22:14:31 (10409) [INFO] * 2025-09-18 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-18 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-18 22:14:31 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-18 22:14:31 (10379) [INFO] * 2025-09-18 22:14:35 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-18 22:14:35 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-18 22:14:35 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-18 22:14:35 (10379) [INFO] * 2025-09-18 22:14:39 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-18 22:14:39 (10379) [INFO] * 2025-09-18 22:14:39 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 22:14:39 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-18 22:14:40 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-18 22:14:40 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-18 22:14:40 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-18 22:14:40 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-18 22:14:40 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-18 22:14:40 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-18 22:14:40 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-18 22:14:40 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-18 22:14:40 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-18 22:14:40 (10392) [INFO] yum --disablerepo= ... * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-18 22:14:40 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-18 22:14:40 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] yum-config-manager --disable * 2025-09-18 22:14:40 (10392) [INFO] or * 2025-09-18 22:14:40 (10392) [INFO] subscription-manager repos --disable= * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-18 22:14:40 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-18 22:14:40 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-18 22:14:40 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-18 22:14:40 (10392) [INFO] compromise: * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-18 22:14:40 (10392) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-18 22:14:40 (10392) [INFO] * free 0 * 2025-09-18 22:14:40 (10392) [INFO] * needed 100 k * 2025-09-18 22:14:40 (10409) [INFO] * 2025-09-18 22:14:40 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-18 22:14:40 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-18 22:14:40 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-18 22:14:40 (10379) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 22:14:40 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-18 22:14:40 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-18 22:14:40 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-18 22:14:40 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-18 22:14:40 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-18 22:14:40 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-18 22:14:40 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-18 22:14:40 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-18 22:14:40 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-18 22:14:40 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-18 22:14:40 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-18 22:14:40 (10409) [INFO] * 2025-09-18 22:14:40 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-18 22:14:40 (10379) [INFO] * 2025-09-18 22:14:40 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-18 22:14:40 (10392) [INFO] Determining fastest mirrors * 2025-09-18 22:14:41 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-18 22:14:41 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-18 22:14:41 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-18 22:14:41 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-18 22:14:41 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-18 22:14:41 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-18 22:14:41 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-18 22:14:41 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-18 22:14:41 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-18 22:14:41 (10392) [INFO] yum --disablerepo= ... * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-18 22:14:41 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-18 22:14:41 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] yum-config-manager --disable * 2025-09-18 22:14:41 (10392) [INFO] or * 2025-09-18 22:14:41 (10392) [INFO] subscription-manager repos --disable= * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-18 22:14:41 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-18 22:14:41 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-18 22:14:41 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-18 22:14:41 (10392) [INFO] compromise: * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-18 22:14:41 (10392) [INFO] * 2025-09-18 22:14:41 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-18 22:14:41 (10392) [INFO] * free 0 * 2025-09-18 22:14:41 (10392) [INFO] * needed 100 k * 2025-09-18 22:14:41 (10409) [INFO] * 2025-09-18 22:14:41 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-18 22:14:41 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-18 22:14:42 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-18 22:14:43 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_mek4ON2Au/ea_profile.json * 2025-09-18 22:14:43 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_mek4ON2Au/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-18 22:14:43 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-19 22:13:35 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-19 22:13:35 (11465) [INFO] Script is up to date. * 2025-09-19 22:13:37 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-19 22:13:37 (10379) [INFO] * 2025-09-19 22:14:17 (10409) [INFO] * 2025-09-19 22:14:17 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-19 22:14:17 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-19 22:14:17 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-19 22:14:17 (10379) [INFO] * 2025-09-19 22:14:20 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-19 22:14:20 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-19 22:14:20 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-19 22:14:20 (10379) [INFO] * 2025-09-19 22:14:23 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-19 22:14:23 (10379) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 22:14:23 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-19 22:14:23 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-19 22:14:23 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-19 22:14:23 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-19 22:14:23 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-19 22:14:23 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-19 22:14:23 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-19 22:14:23 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-19 22:14:23 (10392) [INFO] yum --disablerepo= ... * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-19 22:14:23 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-19 22:14:23 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] yum-config-manager --disable * 2025-09-19 22:14:23 (10392) [INFO] or * 2025-09-19 22:14:23 (10392) [INFO] subscription-manager repos --disable= * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-19 22:14:23 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-19 22:14:23 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-19 22:14:23 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-19 22:14:23 (10392) [INFO] compromise: * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-19 22:14:23 (10392) [INFO] * 2025-09-19 22:14:23 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-19 22:14:23 (10392) [INFO] * free 0 * 2025-09-19 22:14:23 (10392) [INFO] * needed 100 k * 2025-09-19 22:14:23 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-19 22:14:23 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-19 22:14:23 (10409) [INFO] * 2025-09-19 22:14:23 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-19 22:14:23 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-19 22:14:23 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-19 22:14:23 (10379) [INFO] * 2025-09-19 22:14:24 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 22:14:24 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-19 22:14:24 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-19 22:14:24 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-19 22:14:24 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-19 22:14:24 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-19 22:14:24 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-19 22:14:24 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-19 22:14:24 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-19 22:14:24 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-19 22:14:24 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-19 22:14:24 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-19 22:14:24 (10409) [INFO] * 2025-09-19 22:14:24 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-19 22:14:24 (10379) [INFO] * 2025-09-19 22:14:24 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-19 22:14:24 (10392) [INFO] Determining fastest mirrors * 2025-09-19 22:14:25 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-19 22:14:25 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-19 22:14:25 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-19 22:14:25 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-19 22:14:25 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-19 22:14:25 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-19 22:14:25 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-19 22:14:25 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-19 22:14:25 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-19 22:14:25 (10392) [INFO] yum --disablerepo= ... * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-19 22:14:25 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-19 22:14:25 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] yum-config-manager --disable * 2025-09-19 22:14:25 (10392) [INFO] or * 2025-09-19 22:14:25 (10392) [INFO] subscription-manager repos --disable= * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-19 22:14:25 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-19 22:14:25 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-19 22:14:25 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-19 22:14:25 (10392) [INFO] compromise: * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-19 22:14:25 (10392) [INFO] * 2025-09-19 22:14:25 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-19 22:14:25 (10392) [INFO] * free 0 * 2025-09-19 22:14:25 (10392) [INFO] * needed 100 k * 2025-09-19 22:14:25 (10409) [INFO] * 2025-09-19 22:14:25 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-19 22:14:25 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-19 22:14:26 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-19 22:14:26 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rG_pkVKxwF/ea_profile.json * 2025-09-19 22:14:27 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rG_pkVKxwF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-19 22:14:27 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-20 22:14:16 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-20 22:14:16 (11465) [INFO] Script is up to date. * 2025-09-20 22:14:17 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-20 22:14:17 (10379) [INFO] * 2025-09-20 22:14:52 (10409) [INFO] * 2025-09-20 22:14:52 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-20 22:14:52 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-20 22:14:52 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-20 22:14:52 (10379) [INFO] * 2025-09-20 22:14:56 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-20 22:14:56 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-20 22:14:56 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-20 22:14:56 (10379) [INFO] * 2025-09-20 22:15:00 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-20 22:15:00 (10379) [INFO] * 2025-09-20 22:15:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 22:15:00 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-20 22:15:01 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-20 22:15:01 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-20 22:15:01 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-20 22:15:01 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-20 22:15:01 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-20 22:15:01 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-20 22:15:01 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-20 22:15:01 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-20 22:15:01 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-20 22:15:01 (10392) [INFO] yum --disablerepo= ... * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-20 22:15:01 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-20 22:15:01 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] yum-config-manager --disable * 2025-09-20 22:15:01 (10392) [INFO] or * 2025-09-20 22:15:01 (10392) [INFO] subscription-manager repos --disable= * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-20 22:15:01 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-20 22:15:01 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-20 22:15:01 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-20 22:15:01 (10392) [INFO] compromise: * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-20 22:15:01 (10392) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-20 22:15:01 (10392) [INFO] * free 0 * 2025-09-20 22:15:01 (10392) [INFO] * needed 100 k * 2025-09-20 22:15:01 (10409) [INFO] * 2025-09-20 22:15:01 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-20 22:15:01 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-20 22:15:01 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-20 22:15:01 (10379) [INFO] * 2025-09-20 22:15:01 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 22:15:01 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-20 22:15:01 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-20 22:15:01 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-20 22:15:01 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-20 22:15:01 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-20 22:15:01 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-20 22:15:01 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-20 22:15:01 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-20 22:15:01 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-20 22:15:01 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-20 22:15:01 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-20 22:15:01 (10409) [INFO] * 2025-09-20 22:15:01 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-20 22:15:01 (10379) [INFO] * 2025-09-20 22:15:02 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-20 22:15:02 (10392) [INFO] Determining fastest mirrors * 2025-09-20 22:15:05 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-20 22:15:05 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-20 22:15:05 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-20 22:15:05 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-20 22:15:05 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-20 22:15:05 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-20 22:15:05 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-20 22:15:05 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-20 22:15:05 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-20 22:15:05 (10392) [INFO] yum --disablerepo= ... * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-20 22:15:05 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-20 22:15:05 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] yum-config-manager --disable * 2025-09-20 22:15:05 (10392) [INFO] or * 2025-09-20 22:15:05 (10392) [INFO] subscription-manager repos --disable= * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-20 22:15:05 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-20 22:15:05 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-20 22:15:05 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-20 22:15:05 (10392) [INFO] compromise: * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-20 22:15:05 (10392) [INFO] * 2025-09-20 22:15:05 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-20 22:15:05 (10392) [INFO] * free 0 * 2025-09-20 22:15:05 (10392) [INFO] * needed 100 k * 2025-09-20 22:15:05 (10409) [INFO] * 2025-09-20 22:15:05 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-20 22:15:05 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-20 22:15:05 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-20 22:15:06 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cnOLhTcpF3/ea_profile.json * 2025-09-20 22:15:07 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cnOLhTcpF3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-20 22:15:07 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-21 22:14:15 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-21 22:14:15 (11465) [INFO] Script is up to date. * 2025-09-21 22:14:16 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-21 22:14:16 (10379) [INFO] * 2025-09-21 22:14:52 (10409) [INFO] * 2025-09-21 22:14:52 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-21 22:14:52 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-21 22:14:52 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-21 22:14:52 (10379) [INFO] * 2025-09-21 22:14:56 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-21 22:14:56 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-21 22:14:56 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-21 22:14:56 (10379) [INFO] * 2025-09-21 22:14:59 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-21 22:14:59 (10379) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 22:15:00 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-21 22:15:00 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-21 22:15:00 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-21 22:15:00 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-21 22:15:00 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-21 22:15:00 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-21 22:15:00 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-21 22:15:00 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-21 22:15:00 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-21 22:15:00 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-21 22:15:00 (10392) [INFO] yum --disablerepo= ... * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-21 22:15:00 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-21 22:15:00 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] yum-config-manager --disable * 2025-09-21 22:15:00 (10392) [INFO] or * 2025-09-21 22:15:00 (10392) [INFO] subscription-manager repos --disable= * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-21 22:15:00 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-21 22:15:00 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-21 22:15:00 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-21 22:15:00 (10392) [INFO] compromise: * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-21 22:15:00 (10392) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-21 22:15:00 (10392) [INFO] * free 0 * 2025-09-21 22:15:00 (10392) [INFO] * needed 100 k * 2025-09-21 22:15:00 (10409) [INFO] * 2025-09-21 22:15:00 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-21 22:15:00 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-21 22:15:00 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-21 22:15:00 (10379) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 22:15:00 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-21 22:15:00 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-21 22:15:00 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-21 22:15:00 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-21 22:15:00 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-21 22:15:00 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-21 22:15:00 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-21 22:15:00 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-21 22:15:00 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-21 22:15:00 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-21 22:15:00 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-21 22:15:00 (10409) [INFO] * 2025-09-21 22:15:00 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-21 22:15:00 (10379) [INFO] * 2025-09-21 22:15:00 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-21 22:15:01 (10392) [INFO] Determining fastest mirrors * 2025-09-21 22:15:03 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-21 22:15:03 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-21 22:15:03 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-21 22:15:03 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-21 22:15:03 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-21 22:15:03 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-21 22:15:03 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-21 22:15:03 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-21 22:15:03 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-21 22:15:03 (10392) [INFO] yum --disablerepo= ... * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-21 22:15:03 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-21 22:15:03 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] yum-config-manager --disable * 2025-09-21 22:15:03 (10392) [INFO] or * 2025-09-21 22:15:03 (10392) [INFO] subscription-manager repos --disable= * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-21 22:15:03 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-21 22:15:03 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-21 22:15:03 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-21 22:15:03 (10392) [INFO] compromise: * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-21 22:15:03 (10392) [INFO] * 2025-09-21 22:15:03 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-21 22:15:03 (10392) [INFO] * free 0 * 2025-09-21 22:15:03 (10392) [INFO] * needed 100 k * 2025-09-21 22:15:03 (10409) [INFO] * 2025-09-21 22:15:03 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-21 22:15:03 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-21 22:15:04 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-21 22:15:04 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/05bMnrnLuA/ea_profile.json * 2025-09-21 22:15:05 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/05bMnrnLuA/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-21 22:15:05 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-22 22:13:56 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-22 22:13:56 (11465) [INFO] Script is up to date. * 2025-09-22 22:13:57 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-22 22:13:57 (10379) [INFO] * 2025-09-22 22:14:38 (10409) [INFO] * 2025-09-22 22:14:38 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-22 22:14:38 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-22 22:14:38 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-22 22:14:38 (10379) [INFO] * 2025-09-22 22:14:42 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-22 22:14:42 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-22 22:14:42 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-22 22:14:42 (10379) [INFO] * 2025-09-22 22:14:44 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-22 22:14:44 (10379) [INFO] * 2025-09-22 22:14:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 22:14:45 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-22 22:14:46 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-22 22:14:46 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-22 22:14:46 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-22 22:14:46 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-22 22:14:46 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-22 22:14:46 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-22 22:14:46 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-22 22:14:46 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-22 22:14:46 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-22 22:14:46 (10392) [INFO] yum --disablerepo= ... * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-22 22:14:46 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-22 22:14:46 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] yum-config-manager --disable * 2025-09-22 22:14:46 (10392) [INFO] or * 2025-09-22 22:14:46 (10392) [INFO] subscription-manager repos --disable= * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-22 22:14:46 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-22 22:14:46 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-22 22:14:46 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-22 22:14:46 (10392) [INFO] compromise: * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-22 22:14:46 (10392) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-22 22:14:46 (10392) [INFO] * free 0 * 2025-09-22 22:14:46 (10392) [INFO] * needed 100 k * 2025-09-22 22:14:46 (10409) [INFO] * 2025-09-22 22:14:46 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-22 22:14:46 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-22 22:14:46 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-22 22:14:46 (10379) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 22:14:46 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-22 22:14:46 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-22 22:14:46 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-22 22:14:46 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-22 22:14:46 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-22 22:14:46 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-22 22:14:46 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-22 22:14:46 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-22 22:14:46 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-22 22:14:46 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-22 22:14:46 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-22 22:14:46 (10409) [INFO] * 2025-09-22 22:14:46 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-22 22:14:46 (10379) [INFO] * 2025-09-22 22:14:46 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-22 22:14:47 (10392) [INFO] Determining fastest mirrors * 2025-09-22 22:14:50 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-22 22:14:50 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-22 22:14:50 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-22 22:14:50 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-22 22:14:50 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-22 22:14:50 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-22 22:14:50 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-22 22:14:50 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-22 22:14:50 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-22 22:14:50 (10392) [INFO] yum --disablerepo= ... * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-22 22:14:50 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-22 22:14:50 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] yum-config-manager --disable * 2025-09-22 22:14:50 (10392) [INFO] or * 2025-09-22 22:14:50 (10392) [INFO] subscription-manager repos --disable= * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-22 22:14:50 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-22 22:14:50 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-22 22:14:50 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-22 22:14:50 (10392) [INFO] compromise: * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-22 22:14:50 (10392) [INFO] * 2025-09-22 22:14:50 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-22 22:14:50 (10392) [INFO] * free 0 * 2025-09-22 22:14:50 (10392) [INFO] * needed 100 k * 2025-09-22 22:14:50 (10409) [INFO] * 2025-09-22 22:14:50 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-22 22:14:50 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-22 22:14:50 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-22 22:14:51 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/arbi3MGX_c/ea_profile.json * 2025-09-22 22:14:51 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/arbi3MGX_c/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-22 22:14:51 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-23 22:13:36 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-23 22:13:36 (11465) [INFO] Script is up to date. * 2025-09-23 22:13:37 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-23 22:13:37 (10379) [INFO] * 2025-09-23 22:14:25 (10409) [INFO] * 2025-09-23 22:14:25 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-23 22:14:25 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.75. * 2025-09-23 22:14:25 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-23 22:14:25 (10379) [INFO] * 2025-09-23 22:14:29 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-23 22:14:29 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-23 22:14:29 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-23 22:14:29 (10379) [INFO] * 2025-09-23 22:14:32 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-23 22:14:32 (10379) [INFO] * 2025-09-23 22:14:32 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 22:14:32 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-23 22:14:33 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-23 22:14:33 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-23 22:14:33 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-23 22:14:33 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-23 22:14:33 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-23 22:14:33 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-23 22:14:33 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-23 22:14:33 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-23 22:14:33 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-23 22:14:33 (10392) [INFO] yum --disablerepo= ... * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-23 22:14:33 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-23 22:14:33 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] yum-config-manager --disable * 2025-09-23 22:14:33 (10392) [INFO] or * 2025-09-23 22:14:33 (10392) [INFO] subscription-manager repos --disable= * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-23 22:14:33 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-23 22:14:33 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-23 22:14:33 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-23 22:14:33 (10392) [INFO] compromise: * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-23 22:14:33 (10392) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-23 22:14:33 (10392) [INFO] * free 0 * 2025-09-23 22:14:33 (10392) [INFO] * needed 100 k * 2025-09-23 22:14:33 (10409) [INFO] * 2025-09-23 22:14:33 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-23 22:14:33 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-23 22:14:33 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-23 22:14:33 (10379) [INFO] * 2025-09-23 22:14:33 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 22:14:33 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-23 22:14:33 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-23 22:14:33 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-23 22:14:33 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-23 22:14:33 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-23 22:14:33 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-23 22:14:33 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-23 22:14:33 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-23 22:14:33 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-23 22:14:33 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-23 22:14:33 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-23 22:14:33 (10409) [INFO] * 2025-09-23 22:14:33 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-23 22:14:33 (10379) [INFO] * 2025-09-23 22:14:34 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-23 22:14:34 (10392) [INFO] Determining fastest mirrors * 2025-09-23 22:14:35 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-23 22:14:35 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-23 22:14:35 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-23 22:14:35 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-23 22:14:35 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-23 22:14:35 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-23 22:14:35 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-23 22:14:35 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-23 22:14:35 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-23 22:14:35 (10392) [INFO] yum --disablerepo= ... * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-23 22:14:35 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-23 22:14:35 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] yum-config-manager --disable * 2025-09-23 22:14:35 (10392) [INFO] or * 2025-09-23 22:14:35 (10392) [INFO] subscription-manager repos --disable= * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-23 22:14:35 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-23 22:14:35 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-23 22:14:35 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-23 22:14:35 (10392) [INFO] compromise: * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-23 22:14:35 (10392) [INFO] * 2025-09-23 22:14:35 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-23 22:14:35 (10392) [INFO] * free 0 * 2025-09-23 22:14:35 (10392) [INFO] * needed 100 k * 2025-09-23 22:14:35 (10409) [INFO] * 2025-09-23 22:14:35 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-23 22:14:35 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-23 22:14:36 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-23 22:14:36 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QT6mGLLkzv/ea_profile.json * 2025-09-23 22:14:37 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QT6mGLLkzv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-23 22:14:37 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-24 22:13:35 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-24 22:13:35 (11465) [INFO] Script is up to date. * 2025-09-24 22:13:36 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-24 22:13:36 (10379) [INFO] * 2025-09-24 22:14:23 (10409) [INFO] * 2025-09-24 22:14:23 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-24 22:14:23 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.76. * 2025-09-24 22:14:23 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-24 22:14:23 (10379) [INFO] * 2025-09-24 22:14:26 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-24 22:14:26 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-24 22:14:26 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-24 22:14:26 (10379) [INFO] * 2025-09-24 22:14:29 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-24 22:14:29 (10379) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 22:14:30 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-24 22:14:30 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-24 22:14:30 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-24 22:14:30 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-24 22:14:30 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-24 22:14:30 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-24 22:14:30 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-24 22:14:30 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-24 22:14:30 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-24 22:14:30 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-24 22:14:30 (10392) [INFO] yum --disablerepo= ... * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-24 22:14:30 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-24 22:14:30 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] yum-config-manager --disable * 2025-09-24 22:14:30 (10392) [INFO] or * 2025-09-24 22:14:30 (10392) [INFO] subscription-manager repos --disable= * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-24 22:14:30 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-24 22:14:30 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-24 22:14:30 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-24 22:14:30 (10392) [INFO] compromise: * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-24 22:14:30 (10392) [INFO] * 2025-09-24 22:14:30 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-24 22:14:30 (10392) [INFO] * free 0 * 2025-09-24 22:14:30 (10392) [INFO] * needed 100 k * 2025-09-24 22:14:30 (10409) [INFO] * 2025-09-24 22:14:30 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-24 22:14:30 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-24 22:14:30 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-24 22:14:30 (10379) [INFO] * 2025-09-24 22:14:31 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 22:14:31 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-24 22:14:31 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-24 22:14:31 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-24 22:14:31 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-24 22:14:31 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-24 22:14:31 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-24 22:14:31 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-24 22:14:31 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-24 22:14:31 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-24 22:14:31 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-24 22:14:31 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-24 22:14:31 (10409) [INFO] * 2025-09-24 22:14:31 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-24 22:14:31 (10379) [INFO] * 2025-09-24 22:14:31 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-24 22:14:31 (10392) [INFO] Determining fastest mirrors * 2025-09-24 22:14:34 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-24 22:14:34 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-24 22:14:34 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-24 22:14:34 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-24 22:14:34 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-24 22:14:34 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-24 22:14:34 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-24 22:14:34 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-24 22:14:34 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-24 22:14:34 (10392) [INFO] yum --disablerepo= ... * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-24 22:14:34 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-24 22:14:34 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] yum-config-manager --disable * 2025-09-24 22:14:34 (10392) [INFO] or * 2025-09-24 22:14:34 (10392) [INFO] subscription-manager repos --disable= * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-24 22:14:34 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-24 22:14:34 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-24 22:14:34 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-24 22:14:34 (10392) [INFO] compromise: * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-24 22:14:34 (10392) [INFO] * 2025-09-24 22:14:34 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-24 22:14:34 (10392) [INFO] * free 0 * 2025-09-24 22:14:34 (10392) [INFO] * needed 100 k * 2025-09-24 22:14:34 (10409) [INFO] * 2025-09-24 22:14:34 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-24 22:14:34 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-24 22:14:34 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-24 22:14:35 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1PWSoz9Zh6/ea_profile.json * 2025-09-24 22:14:35 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1PWSoz9Zh6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-24 22:14:35 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-25 22:13:45 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-25 22:13:45 (11465) [INFO] Script is up to date. * 2025-09-25 22:13:46 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-25 22:13:46 (10379) [INFO] * 2025-09-25 22:14:31 (10409) [INFO] * 2025-09-25 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-25 22:14:31 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.76. * 2025-09-25 22:14:31 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-25 22:14:31 (10379) [INFO] * 2025-09-25 22:14:34 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-25 22:14:34 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-25 22:14:34 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-25 22:14:34 (10379) [INFO] * 2025-09-25 22:14:37 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-25 22:14:37 (10379) [INFO] * 2025-09-25 22:14:38 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 22:14:38 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-25 22:14:39 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-25 22:14:39 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-25 22:14:39 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-25 22:14:39 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-25 22:14:39 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-25 22:14:39 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-25 22:14:39 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-25 22:14:39 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-25 22:14:39 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-25 22:14:39 (10392) [INFO] yum --disablerepo= ... * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-25 22:14:39 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-25 22:14:39 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] yum-config-manager --disable * 2025-09-25 22:14:39 (10392) [INFO] or * 2025-09-25 22:14:39 (10392) [INFO] subscription-manager repos --disable= * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-25 22:14:39 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-25 22:14:39 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-25 22:14:39 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-25 22:14:39 (10392) [INFO] compromise: * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-25 22:14:39 (10392) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-25 22:14:39 (10392) [INFO] * free 0 * 2025-09-25 22:14:39 (10392) [INFO] * needed 100 k * 2025-09-25 22:14:39 (10409) [INFO] * 2025-09-25 22:14:39 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-25 22:14:39 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-25 22:14:39 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-25 22:14:39 (10379) [INFO] * 2025-09-25 22:14:39 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 22:14:39 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-25 22:14:39 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-25 22:14:39 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-25 22:14:39 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-25 22:14:39 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-25 22:14:39 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-25 22:14:39 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-25 22:14:39 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-25 22:14:39 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-25 22:14:39 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-25 22:14:39 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-25 22:14:39 (10409) [INFO] * 2025-09-25 22:14:39 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-25 22:14:39 (10379) [INFO] * 2025-09-25 22:14:40 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-25 22:14:40 (10392) [INFO] Determining fastest mirrors * 2025-09-25 22:14:43 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-25 22:14:43 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-25 22:14:43 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-25 22:14:43 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-25 22:14:43 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-25 22:14:43 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-25 22:14:43 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-25 22:14:43 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-25 22:14:43 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-25 22:14:43 (10392) [INFO] yum --disablerepo= ... * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-25 22:14:43 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-25 22:14:43 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] yum-config-manager --disable * 2025-09-25 22:14:43 (10392) [INFO] or * 2025-09-25 22:14:43 (10392) [INFO] subscription-manager repos --disable= * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-25 22:14:43 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-25 22:14:43 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-25 22:14:43 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-25 22:14:43 (10392) [INFO] compromise: * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-25 22:14:43 (10392) [INFO] * 2025-09-25 22:14:43 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-25 22:14:43 (10392) [INFO] * free 0 * 2025-09-25 22:14:43 (10392) [INFO] * needed 100 k * 2025-09-25 22:14:43 (10409) [INFO] * 2025-09-25 22:14:43 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-25 22:14:43 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-25 22:14:44 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-25 22:14:44 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C8CFxNIIQr/ea_profile.json * 2025-09-25 22:14:45 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C8CFxNIIQr/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-25 22:14:45 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-26 22:13:46 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-26 22:13:46 (11465) [INFO] Script is up to date. * 2025-09-26 22:13:48 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-26 22:13:48 (10379) [INFO] * 2025-09-26 22:14:38 (10409) [INFO] * 2025-09-26 22:14:38 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-26 22:14:38 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-09-26 22:14:38 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-26 22:14:38 (10379) [INFO] * 2025-09-26 22:14:41 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-26 22:14:41 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-26 22:14:41 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-26 22:14:41 (10379) [INFO] * 2025-09-26 22:14:44 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-26 22:14:44 (10379) [INFO] * 2025-09-26 22:14:44 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 22:14:44 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-26 22:14:45 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-26 22:14:45 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-26 22:14:45 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-26 22:14:45 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-26 22:14:45 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-26 22:14:45 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-26 22:14:45 (10392) [INFO] yum --disablerepo= ... * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-26 22:14:45 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-26 22:14:45 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] yum-config-manager --disable * 2025-09-26 22:14:45 (10392) [INFO] or * 2025-09-26 22:14:45 (10392) [INFO] subscription-manager repos --disable= * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-26 22:14:45 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-26 22:14:45 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-26 22:14:45 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-26 22:14:45 (10392) [INFO] compromise: * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-26 22:14:45 (10392) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-26 22:14:45 (10392) [INFO] * free 0 * 2025-09-26 22:14:45 (10392) [INFO] * needed 100 k * 2025-09-26 22:14:45 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-26 22:14:45 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-26 22:14:45 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-26 22:14:45 (10409) [INFO] * 2025-09-26 22:14:45 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-26 22:14:45 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-26 22:14:45 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-26 22:14:45 (10379) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 22:14:45 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-26 22:14:45 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-26 22:14:45 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-26 22:14:45 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-26 22:14:45 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-26 22:14:45 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-26 22:14:45 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-26 22:14:45 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-26 22:14:45 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-26 22:14:45 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-26 22:14:45 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-26 22:14:45 (10409) [INFO] * 2025-09-26 22:14:45 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-26 22:14:45 (10379) [INFO] * 2025-09-26 22:14:45 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-26 22:14:45 (10392) [INFO] Determining fastest mirrors * 2025-09-26 22:14:47 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-26 22:14:47 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-26 22:14:47 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-26 22:14:47 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-26 22:14:47 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-26 22:14:47 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-26 22:14:47 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-26 22:14:47 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-26 22:14:47 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-26 22:14:47 (10392) [INFO] yum --disablerepo= ... * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-26 22:14:47 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-26 22:14:47 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] yum-config-manager --disable * 2025-09-26 22:14:47 (10392) [INFO] or * 2025-09-26 22:14:47 (10392) [INFO] subscription-manager repos --disable= * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-26 22:14:47 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-26 22:14:47 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-26 22:14:47 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-26 22:14:47 (10392) [INFO] compromise: * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-26 22:14:47 (10392) [INFO] * 2025-09-26 22:14:47 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-26 22:14:47 (10392) [INFO] * free 0 * 2025-09-26 22:14:47 (10392) [INFO] * needed 100 k * 2025-09-26 22:14:48 (10409) [INFO] * 2025-09-26 22:14:48 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-26 22:14:48 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-26 22:14:48 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-26 22:14:49 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4oXkdpTKtM/ea_profile.json * 2025-09-26 22:14:49 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4oXkdpTKtM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-26 22:14:49 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-27 22:14:12 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-27 22:14:12 (11465) [INFO] Script is up to date. * 2025-09-27 22:14:13 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-27 22:14:13 (10379) [INFO] * 2025-09-27 22:14:48 (10409) [INFO] * 2025-09-27 22:14:48 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-27 22:14:48 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-09-27 22:14:48 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-27 22:14:48 (10379) [INFO] * 2025-09-27 22:14:52 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-27 22:14:52 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-27 22:14:52 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-27 22:14:52 (10379) [INFO] * 2025-09-27 22:14:56 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-27 22:14:56 (10379) [INFO] * 2025-09-27 22:14:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 22:14:56 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-27 22:14:57 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-27 22:14:57 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-27 22:14:57 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-27 22:14:57 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-27 22:14:57 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-27 22:14:57 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-27 22:14:57 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-27 22:14:57 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-27 22:14:57 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-27 22:14:57 (10392) [INFO] yum --disablerepo= ... * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-27 22:14:57 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-27 22:14:57 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] yum-config-manager --disable * 2025-09-27 22:14:57 (10392) [INFO] or * 2025-09-27 22:14:57 (10392) [INFO] subscription-manager repos --disable= * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-27 22:14:57 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-27 22:14:57 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-27 22:14:57 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-27 22:14:57 (10392) [INFO] compromise: * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-27 22:14:57 (10392) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-27 22:14:57 (10392) [INFO] * free 0 * 2025-09-27 22:14:57 (10392) [INFO] * needed 100 k * 2025-09-27 22:14:57 (10409) [INFO] * 2025-09-27 22:14:57 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-27 22:14:57 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-27 22:14:57 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-27 22:14:57 (10379) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 22:14:57 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-27 22:14:57 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-27 22:14:57 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-27 22:14:57 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-27 22:14:57 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-27 22:14:57 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-27 22:14:57 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-27 22:14:57 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-27 22:14:57 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-27 22:14:57 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-27 22:14:57 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-27 22:14:57 (10409) [INFO] * 2025-09-27 22:14:57 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-27 22:14:57 (10379) [INFO] * 2025-09-27 22:14:57 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-27 22:14:57 (10392) [INFO] Determining fastest mirrors * 2025-09-27 22:14:58 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-27 22:14:58 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-27 22:14:58 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-27 22:14:58 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-27 22:14:58 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-27 22:14:58 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-27 22:14:58 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-27 22:14:58 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-27 22:14:58 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-27 22:14:58 (10392) [INFO] yum --disablerepo= ... * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-27 22:14:58 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-27 22:14:58 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] yum-config-manager --disable * 2025-09-27 22:14:58 (10392) [INFO] or * 2025-09-27 22:14:58 (10392) [INFO] subscription-manager repos --disable= * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-27 22:14:58 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-27 22:14:58 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-27 22:14:58 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-27 22:14:58 (10392) [INFO] compromise: * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-27 22:14:58 (10392) [INFO] * 2025-09-27 22:14:58 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-27 22:14:58 (10392) [INFO] * free 0 * 2025-09-27 22:14:58 (10392) [INFO] * needed 100 k * 2025-09-27 22:14:58 (10409) [INFO] * 2025-09-27 22:14:58 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-27 22:14:58 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-27 22:14:59 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-27 22:15:00 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/muHzqgcswL/ea_profile.json * 2025-09-27 22:15:00 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/muHzqgcswL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-27 22:15:00 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-28 22:14:12 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-28 22:14:12 (11465) [INFO] Script is up to date. * 2025-09-28 22:14:14 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-28 22:14:14 (10379) [INFO] * 2025-09-28 22:14:46 (10409) [INFO] * 2025-09-28 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-28 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-09-28 22:14:46 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-28 22:14:46 (10379) [INFO] * 2025-09-28 22:14:50 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-28 22:14:50 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-28 22:14:50 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-28 22:14:50 (10379) [INFO] * 2025-09-28 22:14:54 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-28 22:14:54 (10379) [INFO] * 2025-09-28 22:14:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 22:14:54 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-28 22:14:56 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-28 22:14:56 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-28 22:14:56 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-28 22:14:56 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-28 22:14:56 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-28 22:14:56 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-28 22:14:56 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-28 22:14:56 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-28 22:14:56 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-28 22:14:56 (10392) [INFO] yum --disablerepo= ... * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-28 22:14:56 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-28 22:14:56 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] yum-config-manager --disable * 2025-09-28 22:14:56 (10392) [INFO] or * 2025-09-28 22:14:56 (10392) [INFO] subscription-manager repos --disable= * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-28 22:14:56 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-28 22:14:56 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-28 22:14:56 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-28 22:14:56 (10392) [INFO] compromise: * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-28 22:14:56 (10392) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-28 22:14:56 (10392) [INFO] * free 0 * 2025-09-28 22:14:56 (10392) [INFO] * needed 100 k * 2025-09-28 22:14:56 (10409) [INFO] * 2025-09-28 22:14:56 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-28 22:14:56 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-28 22:14:56 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-28 22:14:56 (10379) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 22:14:56 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-28 22:14:56 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-28 22:14:56 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-28 22:14:56 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-28 22:14:56 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-28 22:14:56 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-28 22:14:56 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-28 22:14:56 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-28 22:14:56 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-28 22:14:56 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-28 22:14:56 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-28 22:14:56 (10409) [INFO] * 2025-09-28 22:14:56 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-28 22:14:56 (10379) [INFO] * 2025-09-28 22:14:56 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-28 22:14:56 (10392) [INFO] Determining fastest mirrors * 2025-09-28 22:14:58 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-28 22:14:58 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-28 22:14:58 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-28 22:14:58 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-28 22:14:58 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-28 22:14:58 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-28 22:14:58 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-28 22:14:58 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-28 22:14:58 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-28 22:14:58 (10392) [INFO] yum --disablerepo= ... * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-28 22:14:58 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-28 22:14:58 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] yum-config-manager --disable * 2025-09-28 22:14:58 (10392) [INFO] or * 2025-09-28 22:14:58 (10392) [INFO] subscription-manager repos --disable= * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-28 22:14:58 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-28 22:14:58 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-28 22:14:58 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-28 22:14:58 (10392) [INFO] compromise: * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-28 22:14:58 (10392) [INFO] * 2025-09-28 22:14:58 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-28 22:14:58 (10392) [INFO] * free 0 * 2025-09-28 22:14:58 (10392) [INFO] * needed 100 k * 2025-09-28 22:14:58 (10409) [INFO] * 2025-09-28 22:14:58 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-28 22:14:58 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-28 22:14:59 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-28 22:15:00 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9nIRpNJkQ2/ea_profile.json * 2025-09-28 22:15:00 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9nIRpNJkQ2/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-28 22:15:00 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-29 22:13:39 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-29 22:13:39 (11465) [INFO] Script is up to date. * 2025-09-29 22:13:40 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-29 22:13:40 (10379) [INFO] * 2025-09-29 22:14:28 (10409) [INFO] * 2025-09-29 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-29 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-09-29 22:14:28 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-29 22:14:28 (10379) [INFO] * 2025-09-29 22:14:33 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-29 22:14:33 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-29 22:14:33 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-29 22:14:33 (10379) [INFO] * 2025-09-29 22:14:36 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-29 22:14:36 (10379) [INFO] * 2025-09-29 22:14:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 22:14:36 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-29 22:14:37 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-29 22:14:37 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-29 22:14:37 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-29 22:14:37 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-29 22:14:37 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-29 22:14:37 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-29 22:14:37 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-29 22:14:37 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-29 22:14:37 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-29 22:14:37 (10392) [INFO] yum --disablerepo= ... * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-29 22:14:37 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-29 22:14:37 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] yum-config-manager --disable * 2025-09-29 22:14:37 (10392) [INFO] or * 2025-09-29 22:14:37 (10392) [INFO] subscription-manager repos --disable= * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-29 22:14:37 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-29 22:14:37 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-29 22:14:37 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-29 22:14:37 (10392) [INFO] compromise: * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-29 22:14:37 (10392) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-29 22:14:37 (10392) [INFO] * free 0 * 2025-09-29 22:14:37 (10392) [INFO] * needed 100 k * 2025-09-29 22:14:37 (10409) [INFO] * 2025-09-29 22:14:37 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-29 22:14:37 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-29 22:14:37 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-29 22:14:37 (10379) [INFO] * 2025-09-29 22:14:37 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 22:14:37 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-29 22:14:37 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-29 22:14:37 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-29 22:14:37 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-29 22:14:37 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-29 22:14:37 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-29 22:14:37 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-29 22:14:37 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-29 22:14:37 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-29 22:14:37 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-29 22:14:37 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-29 22:14:37 (10409) [INFO] * 2025-09-29 22:14:37 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-29 22:14:37 (10379) [INFO] * 2025-09-29 22:14:38 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-29 22:14:38 (10392) [INFO] Determining fastest mirrors * 2025-09-29 22:14:39 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-29 22:14:39 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-29 22:14:39 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-29 22:14:39 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-29 22:14:39 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-29 22:14:39 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-29 22:14:39 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-29 22:14:39 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-29 22:14:39 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-29 22:14:39 (10392) [INFO] yum --disablerepo= ... * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-29 22:14:39 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-29 22:14:39 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] yum-config-manager --disable * 2025-09-29 22:14:39 (10392) [INFO] or * 2025-09-29 22:14:39 (10392) [INFO] subscription-manager repos --disable= * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-29 22:14:39 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-29 22:14:39 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-29 22:14:39 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-29 22:14:39 (10392) [INFO] compromise: * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-29 22:14:39 (10392) [INFO] * 2025-09-29 22:14:39 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-29 22:14:39 (10392) [INFO] * free 0 * 2025-09-29 22:14:39 (10392) [INFO] * needed 100 k * 2025-09-29 22:14:39 (10409) [INFO] * 2025-09-29 22:14:39 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-29 22:14:39 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-29 22:14:39 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-29 22:14:40 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9GiYsGO0Gj/ea_profile.json * 2025-09-29 22:14:41 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9GiYsGO0Gj/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-29 22:14:41 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-09-30 22:14:05 (11443) [INFO] Self-update of script version 71 requested. * 2025-09-30 22:14:05 (11465) [INFO] Script is up to date. * 2025-09-30 22:14:06 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-09-30 22:14:06 (10379) [INFO] * 2025-09-30 22:14:46 (10409) [INFO] * 2025-09-30 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-09-30 22:14:46 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-09-30 22:14:46 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-09-30 22:14:46 (10379) [INFO] * 2025-09-30 22:14:48 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-09-30 22:14:48 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-09-30 22:14:48 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-09-30 22:14:48 (10379) [INFO] * 2025-09-30 22:14:51 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-30 22:14:51 (10379) [INFO] * 2025-09-30 22:14:51 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 22:14:51 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-09-30 22:14:54 (10392) [INFO] * EA4: 89.222.122.161 * 2025-09-30 22:14:54 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-09-30 22:14:54 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-09-30 22:14:54 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-30 22:14:54 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-30 22:14:54 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-30 22:14:54 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-30 22:14:54 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-30 22:14:54 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-30 22:14:54 (10392) [INFO] yum --disablerepo= ... * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-30 22:14:54 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-30 22:14:54 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] yum-config-manager --disable * 2025-09-30 22:14:54 (10392) [INFO] or * 2025-09-30 22:14:54 (10392) [INFO] subscription-manager repos --disable= * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-30 22:14:54 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-30 22:14:54 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-30 22:14:54 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-30 22:14:54 (10392) [INFO] compromise: * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-30 22:14:54 (10392) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-30 22:14:54 (10392) [INFO] * free 0 * 2025-09-30 22:14:54 (10392) [INFO] * needed 100 k * 2025-09-30 22:14:54 (10409) [INFO] * 2025-09-30 22:14:54 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-30 22:14:54 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-09-30 22:14:54 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-09-30 22:14:54 (10379) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 22:14:54 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-09-30 22:14:54 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-09-30 22:14:54 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-09-30 22:14:54 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-09-30 22:14:54 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-09-30 22:14:54 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-09-30 22:14:54 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-09-30 22:14:54 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-09-30 22:14:54 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-09-30 22:14:54 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-09-30 22:14:54 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-09-30 22:14:54 (10409) [INFO] * 2025-09-30 22:14:54 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-09-30 22:14:54 (10379) [INFO] * 2025-09-30 22:14:54 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-09-30 22:14:54 (10392) [INFO] Determining fastest mirrors * 2025-09-30 22:14:56 (10392) [INFO] * EA4: 89.222.122.163 * 2025-09-30 22:14:56 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-09-30 22:14:56 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-09-30 22:14:56 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-09-30 22:14:56 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-09-30 22:14:56 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-09-30 22:14:56 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-09-30 22:14:56 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-09-30 22:14:56 (10392) [INFO] packages for the previous distribution release still work). * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-09-30 22:14:56 (10392) [INFO] yum --disablerepo= ... * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-09-30 22:14:56 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-09-30 22:14:56 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] yum-config-manager --disable * 2025-09-30 22:14:56 (10392) [INFO] or * 2025-09-30 22:14:56 (10392) [INFO] subscription-manager repos --disable= * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-09-30 22:14:56 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-09-30 22:14:56 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-09-30 22:14:56 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-09-30 22:14:56 (10392) [INFO] compromise: * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-09-30 22:14:56 (10392) [INFO] * 2025-09-30 22:14:56 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-09-30 22:14:56 (10392) [INFO] * free 0 * 2025-09-30 22:14:56 (10392) [INFO] * needed 100 k * 2025-09-30 22:14:56 (10409) [INFO] * 2025-09-30 22:14:56 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-09-30 22:14:56 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-09-30 22:14:57 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-09-30 22:14:57 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g5wLxAXlTc/ea_profile.json * 2025-09-30 22:14:58 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g5wLxAXlTc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-09-30 22:14:58 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-01 22:13:38 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-01 22:13:38 (11465) [INFO] Script is up to date. * 2025-10-01 22:13:39 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-01 22:13:39 (10379) [INFO] * 2025-10-01 22:14:28 (10409) [INFO] * 2025-10-01 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-10-01 22:14:28 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-10-01 22:14:28 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-01 22:14:28 (10379) [INFO] * 2025-10-01 22:14:32 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-10-01 22:14:32 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-01 22:14:32 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-01 22:14:32 (10379) [INFO] * 2025-10-01 22:14:35 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-01 22:14:35 (10379) [INFO] * 2025-10-01 22:14:35 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 22:14:35 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-01 22:14:36 (10392) [INFO] * EA4: 89.222.122.163 * 2025-10-01 22:14:36 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-10-01 22:14:36 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-10-01 22:14:36 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-01 22:14:36 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-01 22:14:36 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-01 22:14:36 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-01 22:14:36 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-01 22:14:36 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-01 22:14:36 (10392) [INFO] yum --disablerepo= ... * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-01 22:14:36 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-01 22:14:36 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] yum-config-manager --disable * 2025-10-01 22:14:36 (10392) [INFO] or * 2025-10-01 22:14:36 (10392) [INFO] subscription-manager repos --disable= * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-01 22:14:36 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-01 22:14:36 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-01 22:14:36 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-01 22:14:36 (10392) [INFO] compromise: * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-01 22:14:36 (10392) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-10-01 22:14:36 (10392) [INFO] * free 0 * 2025-10-01 22:14:36 (10392) [INFO] * needed 100 k * 2025-10-01 22:14:36 (10409) [INFO] * 2025-10-01 22:14:36 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-10-01 22:14:36 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-01 22:14:36 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-01 22:14:36 (10379) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 22:14:36 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-10-01 22:14:36 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-10-01 22:14:36 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-10-01 22:14:36 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-10-01 22:14:36 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-01 22:14:36 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-01 22:14:36 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-10-01 22:14:36 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-10-01 22:14:36 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-10-01 22:14:36 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-01 22:14:36 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-10-01 22:14:36 (10409) [INFO] * 2025-10-01 22:14:36 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-01 22:14:36 (10379) [INFO] * 2025-10-01 22:14:36 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-01 22:14:36 (10392) [INFO] Determining fastest mirrors * 2025-10-01 22:14:38 (10392) [INFO] * EA4: 89.222.122.163 * 2025-10-01 22:14:38 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.163 * 2025-10-01 22:14:38 (10392) [INFO] * cpanel-plugins: 89.222.122.163 * 2025-10-01 22:14:38 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-01 22:14:38 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-01 22:14:38 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-01 22:14:38 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-01 22:14:38 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-01 22:14:38 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-01 22:14:38 (10392) [INFO] yum --disablerepo= ... * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-01 22:14:38 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-01 22:14:38 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] yum-config-manager --disable * 2025-10-01 22:14:38 (10392) [INFO] or * 2025-10-01 22:14:38 (10392) [INFO] subscription-manager repos --disable= * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-01 22:14:38 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-01 22:14:38 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-01 22:14:38 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-01 22:14:38 (10392) [INFO] compromise: * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-01 22:14:38 (10392) [INFO] * 2025-10-01 22:14:38 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-10-01 22:14:38 (10392) [INFO] * free 0 * 2025-10-01 22:14:38 (10392) [INFO] * needed 100 k * 2025-10-01 22:14:38 (10409) [INFO] * 2025-10-01 22:14:38 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-10-01 22:14:38 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-10-01 22:14:39 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-01 22:14:39 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qAubPr6QVa/ea_profile.json * 2025-10-01 22:14:40 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qAubPr6QVa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-01 22:14:40 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/ * 2025-10-02 22:13:36 (11443) [INFO] Self-update of script version 71 requested. * 2025-10-02 22:13:36 (11465) [INFO] Script is up to date. * 2025-10-02 22:13:37 (10378) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only * 2025-10-02 22:13:37 (10379) [INFO] * 2025-10-02 22:14:14 (10409) [INFO] * 2025-10-02 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** disk space issue * 2025-10-02 22:14:14 (262) [ERROR] *** Elevation Blocker detected: *** This installation of cPanel (11.110.0.50) does not appear to be up to date. Please upgrade cPanel to 11.110.0.77. * 2025-10-02 22:14:14 (10378) [INFO] Running: /usr/bin/imunify360-agent version --json * 2025-10-02 22:14:14 (10379) [INFO] * 2025-10-02 22:14:17 (4432) [WARN] You have MySQL 5.7 installed. This version is not available for AlmaLinux 8. * 2025-10-02 22:14:17 (4439) [INFO] You can manually upgrade your installation of MySQL using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 Once the MySQL upgrade is finished, you can then retry to elevate to AlmaLinux 8. * 2025-10-02 22:14:17 (10378) [INFO] Running: /usr/bin/yum list extras * 2025-10-02 22:14:17 (10379) [INFO] * 2025-10-02 22:14:20 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-02 22:14:20 (10379) [INFO] * 2025-10-02 22:14:20 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 22:14:20 (10392) [INFO] Loading mirror speeds from cached hostfile * 2025-10-02 22:14:21 (10392) [INFO] * EA4: 89.222.122.161 * 2025-10-02 22:14:21 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-10-02 22:14:21 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-10-02 22:14:21 (10392) [INFO] * epel: d2lzkl7pfhq30w.cloudfront.net * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-02 22:14:21 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-02 22:14:21 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-02 22:14:21 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-02 22:14:21 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-02 22:14:21 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-02 22:14:21 (10392) [INFO] yum --disablerepo= ... * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-02 22:14:21 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-02 22:14:21 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] yum-config-manager --disable * 2025-10-02 22:14:21 (10392) [INFO] or * 2025-10-02 22:14:21 (10392) [INFO] subscription-manager repos --disable= * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-02 22:14:21 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-02 22:14:21 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-02 22:14:21 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-02 22:14:21 (10392) [INFO] compromise: * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-02 22:14:21 (10392) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-10-02 22:14:21 (10392) [INFO] * free 0 * 2025-10-02 22:14:21 (10392) [INFO] * needed 100 k * 2025-10-02 22:14:21 (10409) [INFO] * 2025-10-02 22:14:21 (6433) [WARN] Initial run of "yum makecache" failed: One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-10-02 22:14:21 (6434) [WARN] Running "yum clean all" in an attempt to fix yum * 2025-10-02 22:14:21 (10378) [INFO] Running: /usr/bin/yum clean all * 2025-10-02 22:14:21 (10379) [INFO] * 2025-10-02 22:14:21 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 22:14:22 (10392) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base * 2025-10-02 22:14:22 (10392) [INFO] : centos7-els centos7els-rollout-1 centos7els-rollout-2 * 2025-10-02 22:14:22 (10392) [INFO] : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5 * 2025-10-02 22:14:22 (10392) [INFO] : centos7els-rollout-6 epel extras imunify360 imunify360-rollout-1 * 2025-10-02 22:14:22 (10392) [INFO] : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4 * 2025-10-02 22:14:22 (10392) [INFO] : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7 * 2025-10-02 22:14:22 (10392) [INFO] : imunify360-rollout-8 mysql-connectors-community * 2025-10-02 22:14:22 (10392) [INFO] : mysql-tools-community mysql57-community updates * 2025-10-02 22:14:22 (10392) [INFO] : wp-toolkit-cpanel wp-toolkit-thirdparties * 2025-10-02 22:14:22 (10392) [INFO] Cleaning up list of fastest mirrors * 2025-10-02 22:14:22 (10392) [INFO] Other repos take up 2.1 M of disk space (use --verbose for details) * 2025-10-02 22:14:22 (10409) [INFO] * 2025-10-02 22:14:22 (10378) [INFO] Running: /usr/bin/yum makecache * 2025-10-02 22:14:22 (10379) [INFO] * 2025-10-02 22:14:22 (10392) [INFO] Loaded plugins: fastestmirror, universal-hooks * 2025-10-02 22:14:22 (10392) [INFO] Determining fastest mirrors * 2025-10-02 22:14:23 (10392) [INFO] * EA4: 89.222.122.161 * 2025-10-02 22:14:23 (10392) [INFO] * cpanel-addons-production-feed: 89.222.122.161 * 2025-10-02 22:14:23 (10392) [INFO] * cpanel-plugins: 89.222.122.161 * 2025-10-02 22:14:23 (10392) [INFO] * epel: ftp-stud.hs-esslingen.de * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] One of the configured repositories failed (Unknown), * 2025-10-02 22:14:23 (10392) [INFO] and yum doesn't have enough cached data to continue. At this point the only * 2025-10-02 22:14:23 (10392) [INFO] safe thing yum can do is fail. There are a few ways to work "fix" this: * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] 1. Contact the upstream for the repository and get them to fix the problem. * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] 2. Reconfigure the baseurl/etc. for the repository, to point to a working * 2025-10-02 22:14:23 (10392) [INFO] upstream. This is most often useful if you are using a newer * 2025-10-02 22:14:23 (10392) [INFO] distribution release than is supported by the repository (and the * 2025-10-02 22:14:23 (10392) [INFO] packages for the previous distribution release still work). * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] 3. Run the command with the repository temporarily disabled * 2025-10-02 22:14:23 (10392) [INFO] yum --disablerepo= ... * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] 4. Disable the repository permanently, so yum won't use it by default. Yum * 2025-10-02 22:14:23 (10392) [INFO] will then just ignore the repository until you permanently enable it * 2025-10-02 22:14:23 (10392) [INFO] again or use --enablerepo for temporary usage: * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] yum-config-manager --disable * 2025-10-02 22:14:23 (10392) [INFO] or * 2025-10-02 22:14:23 (10392) [INFO] subscription-manager repos --disable= * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] 5. Configure the failing repository to be skipped, if it is unavailable. * 2025-10-02 22:14:23 (10392) [INFO] Note that yum will try to contact the repo. when it runs most commands, * 2025-10-02 22:14:23 (10392) [INFO] so will have to try and fail each time (and thus. yum will be be much * 2025-10-02 22:14:23 (10392) [INFO] slower). If it is a very temporary problem though, this is often a nice * 2025-10-02 22:14:23 (10392) [INFO] compromise: * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] yum-config-manager --save --setopt=.skip_if_unavailable=true * 2025-10-02 22:14:23 (10392) [INFO] * 2025-10-02 22:14:23 (10392) [INFO] Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * 2025-10-02 22:14:23 (10392) [INFO] * free 0 * 2025-10-02 22:14:23 (10392) [INFO] * needed 100 k * 2025-10-02 22:14:23 (10409) [INFO] * 2025-10-02 22:14:23 (6443) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading. If you need assistance, open 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-10-02 22:14:23 (6444) [ERROR] One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo= ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable or subscription-manager repos --disable= 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=.skip_if_unavailable=true Insufficient space in download directory /var/cache/yum/x86_64/7/EA4 * free 0 * needed 100 k * 2025-10-02 22:14:24 (2347) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8. * 2025-10-02 22:14:24 (9452) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cou2LppvzY/ea_profile.json * 2025-10-02 22:14:25 (538) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cou2LppvzY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9454. * 2025-10-02 22:14:25 (479) [WARN] Please fix the detected issues before performing the elevation process. Read More: https://cpanel.github.io/elevate/blockers/